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.

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" <(E-Mail Removed)> wrote in message
news:0E860139-9AD6-4AA9-949C-(E-Mail Removed)...
> 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.

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" <(E-Mail Removed)> wrote in message
> news:0E860139-9AD6-4AA9-949C-(E-Mail Removed)...
> > 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.
>
>
>

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" <(E-Mail Removed)> wrote in message
news:8C33A7DC-0B05-4671-A88B-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
>> news:0E860139-9AD6-4AA9-949C-(E-Mail Removed)...
>> > 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.
>>
>>
>>

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" <(E-Mail Removed)> wrote in message
> news:8C33A7DC-0B05-4671-A88B-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:0E860139-9AD6-4AA9-949C-(E-Mail Removed)...
> >> > 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.
> >>
> >>
> >>
>
>
>

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" <(E-Mail Removed)> wrote in message
> news:8C33A7DC-0B05-4671-A88B-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:0E860139-9AD6-4AA9-949C-(E-Mail Removed)...
> >> > 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.
> >>
> >>
> >>
>
>
>

Did you make sure that all of your users have each one their own copy of the
ADP database file? Second, is this server on a cluster with (more or less)
frequent switching between nodes? For how long did it take before the same
errors came back again?

The size of the ADE file and the fact that this is a named instance should
not be a problem. However, in the case of a named instance, the SQL-Browser
Service is necessary for the SQL OLEDB Provider to discover the port to use
to communicate over TCP/IP; so maybe by specifying the TCP/IP address of the
server followed by the port number (10.10.2.1,1535 instead of the
TheServerName) for example would be better. You can even try to create and
use an Alias for the server instance. This will take the SQL-Browser
Service out of the equation.

A second possibility would be to use the Named Pipes protocol instead of
TCP/IP or vice-versa. Add the prefix tcp: or np: before the name of the
server and in the case of tcp:, don't forget to try with or without the port
used by the instance. Instead of using these prefixes, you can define and
use an Alias, of course. With an Alias, you have a much better control over
the protocol and the port used for the communication.

For the rest, I'm not a network expert myself.

--
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" <(E-Mail Removed)> wrote in message
news:514D0AA4-4666-4D7A-91D4-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
>> news:8C33A7DC-0B05-4671-A88B-(E-Mail Removed)...
>> > 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" <(E-Mail Removed)> wrote in message
>> >> news:0E860139-9AD6-4AA9-949C-(E-Mail Removed)...
>> >> > 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.
>> >>
>> >>
>> >>
>>
>>
>>

Did you make sure that all of your users have each one their own copy of the
ADP database file? Second, is this server on a cluster with (more or less)
frequent switching between nodes? For how long did it take before the same
errors came back again?

The size of the ADE file and the fact that this is a named instance should
not be a problem. However, in the case of a named instance, the SQL-Browser
Service is necessary for the SQL OLEDB Provider to discover the port to use
to communicate over TCP/IP; so maybe by specifying the TCP/IP address of the
server followed by the port number (10.10.2.1,1535 instead of the
TheServerName) for example would be better. You can even try to create and
use an Alias for the server instance. This will take the SQL-Browser
Service out of the equation.

A second possibility would be to use the Named Pipes protocol instead of
TCP/IP or vice-versa. Add the prefix tcp: or np: before the name of the
server and in the case of tcp:, don't forget to try with or without the port
used by the instance. Instead of using these prefixes, you can define and
use an Alias, of course. With an Alias, you have a much better control over
the protocol and the port used for the communication.

For the rest, I'm not a network expert myself.

--
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" <(E-Mail Removed)> wrote in message
news:514D0AA4-4666-4D7A-91D4-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
>> news:8C33A7DC-0B05-4671-A88B-(E-Mail Removed)...
>> > 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" <(E-Mail Removed)> wrote in message
>> >> news:0E860139-9AD6-4AA9-949C-(E-Mail Removed)...
>> >> > 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.
>> >>
>> >>
>> >>
>>
>>
>>

Thanks for your respose Sylvain
Absolutely ADP is local - tests if current drive is a network and won't run
if it is .
I think we are talking about a single server machine though I will ask the
question.

If I use URL and port how do I find the port to use?
Does the instance still go on the end eg 10.10.2.1,1535\SQL2005 ?
Afraid I don't know about Aliases and how to create them. Could you explain
please?
Thanks


"Sylvain Lafontaine" wrote:

> Did you make sure that all of your users have each one their own copy of the
> ADP database file? Second, is this server on a cluster with (more or less)
> frequent switching between nodes? For how long did it take before the same
> errors came back again?
>
> The size of the ADE file and the fact that this is a named instance should
> not be a problem. However, in the case of a named instance, the SQL-Browser
> Service is necessary for the SQL OLEDB Provider to discover the port to use
> to communicate over TCP/IP; so maybe by specifying the TCP/IP address of the
> server followed by the port number (10.10.2.1,1535 instead of the
> TheServerName) for example would be better. You can even try to create and
> use an Alias for the server instance. This will take the SQL-Browser
> Service out of the equation.
>
> A second possibility would be to use the Named Pipes protocol instead of
> TCP/IP or vice-versa. Add the prefix tcp: or np: before the name of the
> server and in the case of tcp:, don't forget to try with or without the port
> used by the instance. Instead of using these prefixes, you can define and
> use an Alias, of course. With an Alias, you have a much better control over
> the protocol and the port used for the communication.
>
> For the rest, I'm not a network expert myself.
>
> --
> 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" <(E-Mail Removed)> wrote in message
> news:514D0AA4-4666-4D7A-91D4-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:8C33A7DC-0B05-4671-A88B-(E-Mail Removed)...
> >> > 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" <(E-Mail Removed)> wrote in message
> >> >> news:0E860139-9AD6-4AA9-949C-(E-Mail Removed)...
> >> >> > 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.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Thanks for your respose Sylvain
Absolutely ADP is local - tests if current drive is a network and won't run
if it is .
I think we are talking about a single server machine though I will ask the
question.

If I use URL and port how do I find the port to use?
Does the instance still go on the end eg 10.10.2.1,1535\SQL2005 ?
Afraid I don't know about Aliases and how to create them. Could you explain
please?
Thanks


"Sylvain Lafontaine" wrote:

> Did you make sure that all of your users have each one their own copy of the
> ADP database file? Second, is this server on a cluster with (more or less)
> frequent switching between nodes? For how long did it take before the same
> errors came back again?
>
> The size of the ADE file and the fact that this is a named instance should
> not be a problem. However, in the case of a named instance, the SQL-Browser
> Service is necessary for the SQL OLEDB Provider to discover the port to use
> to communicate over TCP/IP; so maybe by specifying the TCP/IP address of the
> server followed by the port number (10.10.2.1,1535 instead of the
> TheServerName) for example would be better. You can even try to create and
> use an Alias for the server instance. This will take the SQL-Browser
> Service out of the equation.
>
> A second possibility would be to use the Named Pipes protocol instead of
> TCP/IP or vice-versa. Add the prefix tcp: or np: before the name of the
> server and in the case of tcp:, don't forget to try with or without the port
> used by the instance. Instead of using these prefixes, you can define and
> use an Alias, of course. With an Alias, you have a much better control over
> the protocol and the port used for the communication.
>
> For the rest, I'm not a network expert myself.
>
> --
> 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" <(E-Mail Removed)> wrote in message
> news:514D0AA4-4666-4D7A-91D4-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:8C33A7DC-0B05-4671-A88B-(E-Mail Removed)...
> >> > 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" <(E-Mail Removed)> wrote in message
> >> >> news:0E860139-9AD6-4AA9-949C-(E-Mail Removed)...
> >> >> > 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.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>