Re: ADP problems after SQL 2005 Upgrade
- From: barnowl <barnowl@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 May 2009 06:38:02 -0700
Thanks for your response, Sylvain. Unfortunately problems are still occuring.
I totally rebuilt the ADP and made ADE on site.
I tried giving the end users the ADP rather than the ADE. Initially it went
quiet, but now the same errors are coming in.
[DTNETLIB] [ConnectionWrite(send()) General Network Error
is still occuring. Sometimes it appears that Global variables are being lost.
Sometimes cant find forms that patently are there.
They say that no other application is having problems. There is a Net based
app from another 3rd party on the same instance of SQL that seems to be
fine. It is a named instance - would that make any difference? No error is
consistent.
Could it be adp is too big - it compiles down to about 10 MB - should I be
thinking of splitting it up into libraries. Or are there some sql server
settings I should be looking at? In theory the network hardware is newer and
better and they would expect less problems not more. I am more a developer
than a network expert, and getting a bit desperate now.
"Sylvain Lafontaine" wrote:
Importing all objects into a blank ADP is the best thing. Also, some people.
don't recommend to use the /decompile switch because it has not been fully
tested by MS but are suggesting to use instead the old trick of adding and
removing a dummy reference in the References dialog window of the VBA IDE.
Personally, I use the /decompile switch but I'm also using it with the
/repair /compact switches at the same time.
In your case, I suspect that upgrading the SQL-Server from 2000 to 2005 is
not the only thing that has changed. Maybe the new instance don't have
enough memory or is on an overloaded system or on a (virtual) cluster with
frequent switching between nodes?
--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)
"barnowl" <barnowl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8C33A7DC-0B05-4671-A88B-CE47AEC1FE00@xxxxxxxxxxxxxxxx
Thanks Sylvain
I did most of this - built the ade from adp on target machine but did the
decompile on my own system before delivery. Will try the decompile on
site.
Would there be any difference between
a) use Access Decompile switch option and
b) import all objects into a blank ADP?
"Sylvain Lafontaine" wrote:
ADE are like MDE and as such, will often exhibits strange behavior when
the
target machines are not strictly identical in term of Windows versions,
Service Pack applied, etc.
If you have not recreated the ADE after the upgrade to SQL-Server, you
should do it. The best course of action would be to fully decompile the
ADP
file, copy it on the target machine and create the ADE from there. Using
the ADP instead would be even better.
--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam
please)
Independent consultant and remote programming for Access and SQL-Server
(French)
"barnowl" <barnowl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0E860139-9AD6-4AA9-949C-A20EE3000983@xxxxxxxxxxxxxxxx
My customer has moved his SQL to 2005 from 2000.
The new db is a named instance - previously it was not.
I have upgraded my back end database and reconnected the client which
is
Access ADE. Now frequent errors occur (3 - 4 per day per user) -
Connection
Failure (Sometimes [DBNETLIB][ConnectionWrite(send())] but also
failure
to
fill list / combo boxes, and failure to open forms and reports. The
problem
is always temporarily resolved by restarting the ade. Happens with
Access
2003 and 2007. I identified a message form running on a timer as a
possible
culprit and gave them a means to switch it off. Although this has
perhaps
reduced it, it has not cured it. Any suggestions would be appreciated.
- Follow-Ups:
- Re: ADP problems after SQL 2005 Upgrade
- From: Sylvain Lafontaine
- Re: ADP problems after SQL 2005 Upgrade
- References:
- Re: ADP problems after SQL 2005 Upgrade
- From: barnowl
- Re: ADP problems after SQL 2005 Upgrade
- From: Sylvain Lafontaine
- Re: ADP problems after SQL 2005 Upgrade
- Prev by Date: Re: Switch SQL Connections
- Next by Date: Re: ADP problems after SQL 2005 Upgrade
- Previous by thread: Re: ADP problems after SQL 2005 Upgrade
- Next by thread: Re: ADP problems after SQL 2005 Upgrade
- Index(es):
Relevant Pages
|