corruption of 16 bit db when used by both 16 and 32 bit apps 
Author Message
 corruption of 16 bit db when used by both 16 and 32 bit apps

I am experiencing apparent corruption of my Access 2.0 database when it is
used by both 16 bit and 32 bit applications. Is there a problem with using
both 16 and 32 bit when working with Access 2.0?

The 32 bit app uses the 35 to 25 compatability library, and the 16 bit app
uses the 2.5 compatability layer

The project I am working on uses a 32 bit communications application written
in VB5 for file transfers, and a 16 bit application written in VB4 for
preparing the transfer files (providing administrative data, attaching
images, etc.). The database we use is Access 2.0. This is a legacy
application originally written in VB3, and slowly being upgraded as
customers become willing to upgrade hardware and OS.

Any help or suggestions would be greatly appreciated
David M. Nichols



Sat, 02 Jun 2001 03:00:00 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. 32 bit app / 16 bit DB

2. Connect 16-bit VB app to 32-bit Access 97 DB

3. Launching 16-Bit apps from 32-Bit app?

4. Need help calling 16-bit app from 32-bit app

5. Executing a 16 bit app from a 32 bit app

6. VB 4.0 (16-Bit)/Crystal Reports 3.0.1.32 (16-Bit) Print Preview Maximize Window

7. Desperate for help Converting 16 bit app to 32 bit

8. 16 bit app running in 32 bit world

9. DDE between 16 bit and 32 bit apps

10. Calling 16 bit DLL from 32 bit app

11. launching 16 bit app from 32 bit

 

 
Powered by phpBB® Forum Software