Re: 2003 ADP corrupting when cannot connect
- From: petery@xxxxxxxxxxxxxxxxxxxx (Peter Yang [MSFT])
- Date: Tue, 30 Aug 2005 03:24:18 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@xxxxxxxxxxxxxxxxxxxx>
<efl7MIzpFHA.2152@xxxxxxxxxxxxxxxxxxxx>
<eRZVTZzpFHA.1044@xxxxxxxxxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: petery@xxxxxxxxxxxxxxxxxxxx (Peter Yang [MSFT])
| Organization: Microsoft
| Date: Tue, 23 Aug 2005 05:38:25 GMT
| Subject: Re: 2003 ADP corrupting when cannot connect
| X-Tomcat-NG: microsoft.public.access.adp.sqlserver
| Message-ID: <z6FHkT6pFHA.472@xxxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.access.adp.sqlserver
| Lines: 120
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.access.adp.sqlserver:5314
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| 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@xxxxxxxxxxxxxxxxxxxxx>
| | References: <OU$EieypFHA.272@xxxxxxxxxxxxxxxxxxxx>
| <efl7MIzpFHA.2152@xxxxxxxxxxxxxxxxxxxx>
| | Subject: Re: 2003 ADP corrupting when cannot connect
| | Date: Mon, 22 Aug 2005 17:29:12 +0100
| | Lines: 59
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| | X-RFC2646: Format=Flowed; Response
| | Message-ID: <eRZVTZzpFHA.1044@xxxxxxxxxxxxxxxxxxxx>
| | Newsgroups: microsoft.public.access.adp.sqlserver
| | NNTP-Posting-Host: bsoff.tunnel.moving-edge.net 217.22.85.245
| | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.access.adp.sqlserver:5312
| | X-Tomcat-NG: microsoft.public.access.adp.sqlserver
| |
| | 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.
| |
| |
| |
| | "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
| | wrote in message news:efl7MIzpFHA.2152@xxxxxxxxxxxxxxxxxxxxxxx
| | > 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.
| | >
| | > --
| | > Sylvain Lafontaine, ing.
| | > MVP - Technologies Virtual-PC
| | > E-mail: http://cerbermail.com/?QugbLEWINF
| | >
| | >
| | > "Tim Unsted" <penny@xxxxxxxxxxxxxxxxxxxxx> wrote in message
| | > news:OU$EieypFHA.272@xxxxxxxxxxxxxxxxxxxxxxx
| | >>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?
| | >>
| | >>
| | >>
| | >
| | >
| |
| |
| |
|
|
.
- Follow-Ups:
- Re: 2003 ADP corrupting when cannot connect
- From: Tim Unsted
- Re: 2003 ADP corrupting when cannot connect
- References:
- 2003 ADP corrupting when cannot connect
- From: Tim Unsted
- Re: 2003 ADP corrupting when cannot connect
- From: Sylvain Lafontaine
- Re: 2003 ADP corrupting when cannot connect
- From: Tim Unsted
- Re: 2003 ADP corrupting when cannot connect
- From: Peter Yang [MSFT]
- 2003 ADP corrupting when cannot connect
- Prev by Date: (ACCESS or Dot.Net ) + SQL server for a simple multiuser aplication
- Next by Date: Re: (ACCESS or Dot.Net ) + SQL server for a simple multiuser aplication
- Previous by thread: Re: 2003 ADP corrupting when cannot connect
- Next by thread: Re: 2003 ADP corrupting when cannot connect
- Index(es):
Relevant Pages
|