MS Access Forum / SQL Server / ADP / August 2005
2003 ADP corrupting when cannot connect
|
|
Thread rating:  |
Tim Unsted - 22 Aug 2005 15:44 GMT I have an Access ADP, developed and all working happily in Access 2000. However, if I send this to an Access 2003 customer without first disconnenting it (I've put some code in to drop the db connection) then they run into all sorts of problems when they first try to open the ADP at their end. If first says that it cannot connect to 'mydatabase' on 'myserver', hangs and then cannot be opened at all - basically corrupts. Any ideas?
Sylvain Lafontaine - 22 Aug 2005 16:56 GMT The ADP should open on an empty after a few seconds (minutes?) of delay. However, it is possible that you have code to automatically run on startup that will prolong this delay.
In the same way than with a MDB file, there is also the possibility of multiple problems when the file has not been decompiled before transferring it to other versions of Windows and Access (including other versions of Service Packs). You should try a Compact and Repair just before sending it.
 Signature Sylvain Lafontaine, ing. MVP - Technologies Virtual-PC E-mail: http://cerbermail.com/?QugbLEWINF
>I have an Access ADP, developed and all working happily in Access 2000. >However, if I send this to an Access 2003 customer without first [quoted text clipped - 3 lines] >'myserver', hangs and then cannot be opened at all - basically corrupts. >Any ideas? Tim Unsted - 22 Aug 2005 17:29 GMT Thanks Sylvain,
We do always go through the decompile , compile, compact and repair routine before shipping. We also (nearly always) disconnect the ADP. However, this does happen if we don't disconnect it. You're right, if I try it here in our development environment it will sit for up to several minutes and eventually be OK, but I guess the clients are less patient and will attempt to close the ADP as they think it's hung. It's perhaps at this stage that it becomes corrupt. We supply a text file that the ADP reads to perform it's reconnection and if it's been disconnected at this end it then reads this file at startup (while a splash screen is displayed) and all works fine.
Similar behaviour is also happening with clients running on WANs and Citrix or Terminal Services. It'll work OK for maybe a couple of days and then they'll run into the same problems - hanging on starting up and then getting corrupt. The only solution then is to grap a fresh copy. It's almost as if the network connection to the database is not available or perhaps does not have enough necessary bandwidth. Or could it be to do with a Firewall? Sorry, I know very little about networking or Citrix!
I'm at a loss to know why the ADP gets corrupt. I have not come across any other posting here or on other forums that address this same problem.
> The ADP should open on an empty after a few seconds (minutes?) of delay. > However, it is possible that you have code to automatically run on startup [quoted text clipped - 13 lines] >>'myserver', hangs and then cannot be opened at all - basically corrupts. >>Any ideas? Sylvain Lafontaine - 22 Aug 2005 18:45 GMT You're right about your last sentence: you're the first one that I've seen having some sort of corruption problem with ADP once the file has been distributed. The only corruption problems that I've heard of with ADP was when in the development/design process and never while in the production stage because the ADP file is not longer modified at these moments, the only updates taking place on the SQL-Server. The exception to this would be the use of user's properties but I don't see how this could lead to a corrupt ADP file.
In your case, what's the necessity of using Citrix/TS with ADP? This looks to me as a loss of money.
 Signature Sylvain Lafontaine, ing. MVP - Technologies Virtual-PC E-mail: http://cerbermail.com/?QugbLEWINF
> Thanks Sylvain, > [quoted text clipped - 37 lines] >>>'myserver', hangs and then cannot be opened at all - basically corrupts. >>>Any ideas? Tim Unsted - 23 Aug 2005 10:36 GMT What appears to happen is that Access 2003 attempts to establish a connection (using the CurrentProject.BaseConnectString property if it's not been dropped) BEFORE any code runs from the splash screen or an AutoExec macro. Infact, opening the ADP with the SHIFT key held down still gives a warning message that it cannot find "<mydatabase> on <myserver>". It's at this point it hangs - again, even whilst holding the SHIFT key down. This appears to be different behaviour to Access 2000. I wonder if it might be possible to programmatically drop the connection when the application closes, thereby clearing the CurrentProject.BaseConnectString property each time and allowing our routine to reconnect the ADP using the connection string in the text file?
The requirements to run on Citrix/TS are customer requirements- not ours. I'm far happier when installing our products on the user's PC's. In fact, Citrix may not be the issue here, but certainly running the ADP over a WAN seems to cause problems, possibly because of other network traffic or the environment making the connection to the database too slow or even not possible at the time the ADP is opened.
> You're right about your last sentence: you're the first one that I've seen > having some sort of corruption problem with ADP once the file has been [quoted text clipped - 49 lines] >>>>'myserver', hangs and then cannot be opened at all - basically corrupts. >>>>Any ideas? Peter Yang [MSFT] - 24 Aug 2005 08:48 GMT Hello Penny,
You may want to try the following function to make ADP opens in a disconnected state:
Function MakeADPConnectionless() '------------------------------------------------------------ 'This code removes the connection properties from the 'Access Project for troubleshooting purposes. 'The ADP opens in a disconnected state until new connection 'properties are supplied. '------------------------------------------------------------ Application.CurrentProject.OpenConnection "" End Function
884457 How to deploy an Access 2003 project that connects to an existing SQL http://support.microsoft.com/?id=884457
Regards,
Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone support at no charge during critical LAN outages or "business down" situations. This benefit is available 24 hours a day, 7 days a week to all Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS: https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International Support page: http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Tim Unsted" <penny@baileysolutions.co.uk> | References: <OU$EieypFHA.272@TK2MSFTNGP15.phx.gbl> <efl7MIzpFHA.2152@TK2MSFTNGP14.phx.gbl> <eRZVTZzpFHA.1044@tk2msftngp13.phx.gbl> <Oey7KF0pFHA.1088@TK2MSFTNGP14.phx.gbl>
| Subject: Re: 2003 ADP corrupting when cannot connect | Date: Tue, 23 Aug 2005 10:36:59 +0100 [quoted text clipped - 83 lines] | >>>>'myserver', hangs and then cannot be opened at all - basically corrupts. | >>>>Any ideas? Peter Yang [MSFT] - 23 Aug 2005 06:38 GMT Hello Tim,
I agree with you that most likely the clients are less patient and try to close the ADP, which causes corruption.
you may want to control the connection process upon startup so that you can look for errors and handle them accordingly. You may want to refer to the following article to do this:
306881 How to programmatically change the connection of a Microsoft Access http://support.microsoft.com/?id=306881
As for Citrix terminal server issue, you may want to narrow down if the issue disappear when moving the application from the Ctrix. If so, you may want to contact Citrix to get the latest patch or update.
Best Regards,
Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Tim Unsted" <penny@baileysolutions.co.uk> | References: <OU$EieypFHA.272@TK2MSFTNGP15.phx.gbl> <efl7MIzpFHA.2152@TK2MSFTNGP14.phx.gbl>
| Subject: Re: 2003 ADP corrupting when cannot connect | Date: Mon, 22 Aug 2005 17:29:12 +0100 [quoted text clipped - 51 lines] | >>'myserver', hangs and then cannot be opened at all - basically corrupts. | >>Any ideas? Peter Yang [MSFT] - 30 Aug 2005 04:24 GMT Hello Tim,
I'm just checking to see if the info provided was helpful. If you have any questions or concerns, please don't hesitate to let us know.
Thanks & Regards,
Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone support at no charge during critical LAN outages or "business down" situations. This benefit is available 24 hours a day, 7 days a week to all Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS: https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International Support page: http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| X-Tomcat-ID: 104699473 | References: <OU$EieypFHA.272@TK2MSFTNGP15.phx.gbl> <efl7MIzpFHA.2152@TK2MSFTNGP14.phx.gbl> <eRZVTZzpFHA.1044@tk2msftngp13.phx.gbl>
| MIME-Version: 1.0 | Content-Type: text/plain [quoted text clipped - 114 lines] | corrupts. | | >>Any ideas? Tim Unsted - 30 Aug 2005 10:56 GMT Peter,
Yes, thank you. A combination of what you and Sylvain suggested seems to work here, but the proof will be in this working at client sites - not had enough time to test yet. However, the ADP seems more stable and less likely to have connection problems if I make the ADP connectionless and clear the BaseConnectionString property BEFORE attempting a new connection. I've also teaked my code so that should no connection be possible (network unavailable/database server not responding) the APD will quit cleanly, clearing any BaseConnectionString property.
Regards
Tim
> Hello Tim, > [quoted text clipped - 177 lines] > | corrupts. > | | >>Any ideas?
|
|
|