Access 2003 ADP corrupting when cannot connect

[tunsted]

I have an Access ADP that has been developed in Access 2000. All works fine, but if I convert it to Access XP or 2003 then it gets corrupt if it's moved and cannot establish it's previous connection when restarting. Have gone through the usual Decompile, compile, compact and repair. Seems to happen mainly on WANs. Any ideas?

 

[markphsd]

How is it you are connecting. Do you have connection routines to prompt for a connetion, or does it go straight to the sqlserver? I would imagine that you could prevent corruption by first ensuring there is a connetion. And you an better do that with routines.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[tunsted]

The ADP is usually shipped as disconnected - we have a routine that we run to drop the database connection. Otherwise, the ADP remembers it's last good connection (CurrentProject.BaseConnectionString) and tries to reestablish this as it starts. We use a text file that stores the customer's database connection string, and a routine in the ADP reads this as it starts up (whilst a splash screen is displayed) and if the CurrentProject.BaseConnectionString differs to the text file it will drop the BaseConnectionString and re-establish a connection based on what's in the text file. This all works fine for Access 2000 ADPs, but for some reason Access XP/2003 ADPs seem to try to connect BEFORE the splash screen loads (they even try to connect if you open the ADP with the SHIFT key pressed!). If the connection cannot be established a warning message appears, it then hangs and then appears to be corrupt.