I have a VB app that was using OLEDB Jet 4.0 ADO provider for a data control
connection against an Access 97 database running on WIN95 system.  I
switched to OELDB Jet 3.5 to try to eliminate a problem of an update error
against a replicated database.

Now my app reports "ADO provider not found".  I have repackaged my app and
de-installed and reinstalled to make sure it has the right drivers etc. to
no avail.

The program works fine on my NT workstation, BTW.

Any suggestions?

Thanks

Long shot here, but when you refer to OLEDB Jet 3.5, do you mean OLEDB Jet
3.51?  I'm assuming you do, but if you're setting this through code, it
could be an easy mistake to leave off the one.

   I had a similar problem and it was because the oledb provider for Jet
3.5x was not installed on the client machine. Try installing the MDAC file
that comes with Visual Studio (not the last MDAC version because this one
only has Jet 4.0).

   Cheers,

Gustavo Rodrguez

Thanks for the input friends.

Dave, I meant oledb 3.51.  I'm not setting it thru code but thru the
connection builder in designer.

I will try installing the other version of MDAC.  Does anyone know what
file(s) are associated with the 3.51 OLEDB provider?  I noticed that there
is a "msjetoledb40.dll" file in the systems directory but no corresponding
"msjetoledb35.dll"

Thanks again
Bill

The Jet 3.5 provider is or should be in your Program Files Common Directory
going by this name: Msjtor35.dll at least this is the file i struggled with
in some of my apps using Access 97. I think that you should rather use Jet
4.0 it still works with Access 97.

Hugo