sql server connect:
We have built an application (VB 6 with a SQL 2000 backend database)
in-house and from time to time, we get the dbnetlib error message. This error
message seems to happen when the machine is just idle and is driving me nuts.
The error message doesnt seem to have the issue while the user is actively
using the application. Could this problem have something to do with
connection pooling? If anyone has any ideas, it would be much appreciated.

Thanks in advance!

We have seen this from time-to-time. It seems that the connection "ages out"
after a long period of dormancy. The solution I use is to occasionally poll
the server to make sure it knows that the application is still alive. I
don't think it's a connection pooling issue. It looks like the transport
layer is being closed at the server end (in my case).

USE <initial catalog>

is enough to do the job.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

[quoted text, click to view]