Do I need the Microsoft Jet OLE DB Provider on XP SP2 (MDAC 2.8) via VB?

Windows XP SP2 implements MDAC 2.8 - which does not include the Microsoft Jet OLE DB Provider.

So what will the connection string look like without the provider

eg: PROVIDER=Microsoft.Jet.OLEDB.4.0;Data Source=mydatabase.mdb;Jet OLEDB:Database Password=<pwd>

What is the equivalent without the Microsoft Jet OLE DB Provider and without ODBC

.NET Development33

try this:

Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\myFile.mdb;User Id=admin;Password=;

The Microsoft Jet OLEDB Provider is pre-installed on Windows XP SP2.

BTW, if you're running on a version of the OS which does not have the Jet OLEDB Provider installed then you cannot use ADO.NET.

Hi ahmedilyas, thanks for your response...

However your suggested:

"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\myFile.mdb;User Id=admin;Password=;"

seems to imply that the syntax "Jet OLEDB:Database Password" is no longer supported Are you sure about that

Hi Paul, thanks for your reponse...

Are you sure that the Microsoft Jet OLEDB is pre-installed on Windows XP SP2 I have a client whose software (using my example connection string above) is unable to connect to the MS Access database since they upgraded to Windows XP SP2.

Reading the documentation around MDAC I got the impression that

1) MDAC 2.8 is pre-installed with Window XP SP2 and
2) MDAC 2.8 no longer includes the "Microsoft Jet OLEDB"

so I assumed that I now need to reference a different provider or find the "Microsoft Jet OLEDB" provider from a different source

Yes, the Jet Database Engine Components are installed with SP2 on Windows XP. See the following MS KB article:

Information about Jet 4.0 Service Pack 8

The version installed with XP SP2 is 4.0.8618.0. It's a slightly later version than Jet 4.0 SP8.

If the user is having problems connecting I think we would need to know some more details, such as any errors that might be occurring.

Hi Paul - thanks for your response

I have resolved my issue. I was off track thinking that XP SP2 does not support the Jet OLEDB provider - as you stated.

It turns out that my problem was due to a corrupted MDAC. I suspect that the client installed SQL2000 (or some other software) after upgrading to XP SP2. The subsequent installation corrupted the MDAC.

I used the following document to fix the corrupted MDAC and now all is fine

(http://www.macropool.com/en/download/mdac_xp_sp2.html)

Thanks for your help