ADODB.Connection Fails to connect ASP

[ckrotcov]

One of our clients is using the following ASP code to connect to the MS Access DB on IIS 5.

dsn = "dsn=mydb;uid=GOPUser;pwd="""";"
conn.open dsn

It works great for a couple of days. Then it dies on the open code. with the following error.

error '80004005' unspecified error

To fix the problem I comment out pwd=""""; part from the dsn string and it works again for a while. Until it dies again. I put the pwd part back and we are up and running again.

I did notice there are a bunch or ADODB.Recordset objects that get created but either not getting closed or not set to nothing. Would that eventually lead to connection failing to open?

Anyone has any suggestions?

[pclement]

I would highly recommend using Jet OLEDB instead of ODBC (and the MS Access driver) since the technology is more stable. Below is a connection string example:

Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\mydatabase.mdb

[gupex]

Paul,

'I would highly recommend using Jet OLEDB instead of ODBC (and the MS Access driver) since the technology is more stable.'

What are the symptoms one would see if using ODBC? (am starting to get a little worried - have been using ODBC connection for a long time :-(

Greg

BTW - This would allow me to have the user browse to find the d/b (a good thing), and store this info somewhere (typically in the registry) - what would one do for SQL - we have users with SQL and Access using the same .exe

[RobDog888]

If you are leaving recordsets open and not closing/destroying them then that can potentially lead to database issues especially with Access. Usually they create the database corruptions but other issues are potential too.