I agree with Mike on this one.
If you MUST convert to 32Bits no matter what however (or whichever reasons).
Make sure you have the 32bit version of all your custom third party controls
that you might have used.
If you didn't use any, all the good for your porting experience :-).
I did a port from VB4 16 to VB 4 32 and when it exports the forms, tab
orders and Z orders of the forms weren't good afterwards...
If your application makes use of any windows API functions make sure that
you change those to call their 32 bit counterparts and that all variables
getting values from the API Functions are Declared as Long isntead of
Integer like they probably are in your 16 bit version.
In my porting experience, all controls included with VB 4 16 bit should port
to their 32bvit equivalents in VB4 32 bit as it did for me. You might want
to check any grid type controls you have to make sure that went well as you
may need to redefine your column headers and bind then to any DB all over
again...
If you used Crystal reports again I'd check those two although most of your
report should still be working after the port...but just in case :-).
I think with these you should be good to go
--
Stéphane Richard
Senior Software and Technology Supervisor
http://www.totalweb-inc.com
For all your hosting and related needs
"Edward" <te********@hotmail.com> wrote in message
news:25**************************@posting.google.c om...
Years ago I wrote an app in VB 4.0 16 bit. The program is still
selling, but the clients want to upgrade to 32 bit. Should I go for
VB 4.0 32 bit, or version 5, or version 6? There is only a tiny
budget for this, and I don't want to do any rewrites so VB.NET is out!
Also, are there any "gotchas" that I need to be aware of?
many thanks in advance and sorry if this question has been asked and
answered before - I did a search and couldn't find anything.
Edward
