32/16 Bit Code Conversion 
Author Message
 32/16 Bit Code Conversion

I want to convert some apps I have written in VB4.0 32 bit to 16 bit versions I can run under Win
3.1.  Is there a simple way to recompile the application?  Do I need to load the 16 bit version
of VB4.0 and compile it there?  Any help and also problems anyone has run into in doing this
would be greatly appreciated.  Thanks

--------------------------------------------------------------------------
Matthew S. Jordan | If you thought the Time-Warner merger was big, wait

--------------------------------------------------------------------------



Tue, 01 Sep 1998 03:00:00 GMT  
 32/16 Bit Code Conversion

Quote:
>I want to convert some apps I have written in VB4.0 32 bit to 16 bit versions I can run under Win
>3.1.  Is there a simple way to recompile the application?  Do I need to load the 16 bit version
>of VB4.0 and compile it there?

Yes

Quote:
>Any help and also problems anyone has run into in doing this
>would be greatly appreciated.

If you have used any 32 bit OCXs that don't appear as xxxx16.OCX in the
Windows\System dir (ie 32 bit only OCXs), you won't be able to compile it
without re-writing the code.


--
Newbiehood is not a period of time, it's a way of life.

http://www.sn.no/~balchen/
ftp://ftp.sn.no/user/balchen/



Wed, 02 Sep 1998 03:00:00 GMT  
 32/16 Bit Code Conversion

Quote:
>I want to convert some apps I have written in VB4.0 32 bit to 16 bit versions I can run under Win
>3.1.  Is there a simple way to recompile the application?  

Recompile with the 16 bit version of VB4. Provided you don't need to
support VB3 as well, then there are very few problems in doing this.
VB4/16 & VB4/32 are usually much closer than VB4/16 & VB3/16.

Potential Problems:

You'll need to use 16 bit OCXes, instead of 32 bit. These will either
sort themselves out (in most cases), require a new 16 bit OCX from a
third party developer, or may be impossible (the new "'95 style"
controls, like status bars and Tree Views)

If you need tabbed folders, use the SSTab (16 or 32) rather than the
MS TabStrip (32 only)

Be careful with database features. If you're using Jet 3 features,
make sure that they're supported by 16 bit databases, Jet 2.5, and
don't convert your MDB files to 32 bit format.

You may need some explicit DoEvents calls under Win16 that you didn't
need under the 32 bit OSes. If in doubt, include them - they won't
hurt under 32.

Any DLL declares will need to be replaced with 16 bit equivalents. I
assume you do have 16 bit versions of the DLLs themselves.

The Err object has changed slightly under VB4 (no implicit
clear-on-read)

--

If all it takes is an infinite number of monkeys with typewriters,
how come AOL haven't written any Shakespeare yet ?



Mon, 07 Sep 1998 03:00:00 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. API Conversion 16 bit to 32 bit

2. 16-bit to 32-bit conversion problem

3. 16 bit and 32 bit platform conversion

4. VB 4.0 conversion from 32 bit to 16 bit

5. 16-bit to 32-bit DLL conversion

6. 16 bit to 32 bit conversion

7. VB4: 32-bit to 16-bit conversion

8. VB 4 16 bit to 32 bit conversion

9. 16-bit to 32-bit conversion

10. Help, urgent: compiling 16 bit vb 4 coe to 32 bit vb 4 code

11. 16 bit code to 32 bit

 

 
Powered by phpBB® Forum Software