DoCmd.TransferDatabase corrupts on receiving end?

[Ahliana]

We have an app in Access 2000, and we email an update database. The application pulls in parts that it needs, it has done this for quite some time. Then, because we need to replace a module with global variables, we shut down the app, start up the update mdb, and push objects using DoCmd.TransferDatabase.

We are having problems on some computers, but not all, that the modules that get pushed will be corrupted, and all code in them will be lost when we then open up the application.

Does anyone have any knowledge of this, or had any experience with this? Your comments would be very much appreciated.

Ahliana
Argue for your limitations and, sure enough, they're yours! - Richard Bach

 

[VBslammer]

Are you getting the dreaded [tt]"Error accessing file. Network connection may have been lost."[/tt] error? That's a nasty bug that happens when you import code modules on a computer that has Microsoft Access 2000 and version 6.3.91.8 of the Vbe6.dll file installed. See the MSDN article to see if it applies:

Access 2000 Import Bug

VBSlammer

"You just have to know which screws to turn." - Professor Bob