I have an asp application that works with an Access 2000 database.  I have a

friend that installed it on another computer with Access 97 installed.  I

had him upgrade MDAC, but the asp application still cannot open the

database.  I thought perhaps the default Access driver was pointing to the

wrong version of jet, so I had him change the datasource for the application

to be more specific, but the problem continues.



My new connection string now reads:

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



But the following error continues:



Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access 97 Driver] Can't open database

'(unknown)'. It may not be a database that your application recognizes, or

the file may be corrupt.



What really baffles me is the "Access 97 Driver" part of the message when

the provider is pointing to Jet 4.0.  Any pointers?



Bonnie

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

: I have an asp application that works with an Access 2000 database.  I have

a

: friend that installed it on another computer with Access 97 installed.  I

: had him upgrade MDAC, but the asp application still cannot open the

: database.  I thought perhaps the default Access driver was pointing to the

: wrong version of jet, so I had him change the datasource for the

application

: to be more specific, but the problem continues.

:

: My new connection string now reads:

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

:

: But the following error continues:

:

: Microsoft OLE DB Provider for ODBC Drivers error '80004005'

: [Microsoft][ODBC Microsoft Access 97 Driver] Can't open database

: '(unknown)'. It may not be a database that your application recognizes, or

: the file may be corrupt.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



Judging by the error message it *appears* that you are not using the above

connection string to open a connection to your database. Instead you are

still using the OLEDB Provider for ODBC drivers.



Can you post some more code, eg the bits you use to actually open the

connection (If you were actually using the provider above you'd have an

error similar to:



Microsoft JET OLEDB Provider Error '80004005'



not



Microsoft OLE DB Provider for ODBC Drivers error '80004005'



Cheers

Ken