VB6 to Acc 2.0 (Jet 2) Database using ADO (Access 2 / VB6)

Topic

New Reply

Hi

I’ve got an old Access 2.0 database that is being used. Upgrading it to a later version of Acc is not an option.

At present, I have an app (stand alone), written in VB6 to do a whole lot of stuff. One of the steps though needs to read and write data to the Access 2 database.

At present, I am using ADO, and using the Jet.OLEDB.4.0 provider in the connection string. There are other users using the back end database file.

I am getting strange error messages though, like the database is corrupted or something when I just try and read from the database. I am closing and destroying the recordset objects after use in VB.

Is there another provider I should be using other than the Jet 4 OLEDB provider? Are there issues that anyone is aware of?

Your help appreciated.

Reply | Quote

Replies

You could try the 3.51 provider, which might do a better job, but I wouldn’t hold out too much hope for communicating reliably with a 2.0 database. Are you saying that other people are in the database when you’re trying to use ADO to communicate with it?

Reply | Quote

Hi Charlotte,

Yes , other people are in the database, using it when I am also trying to access it with ADO. Those users are using the Access 2 front end application.

What alternative method of accessing it via VB6 would be better do you think? Using DAO instead?

J

Reply | Quote