Deploying a VB 6 and Access database Packag

I'm using ADO 2.0 to connect to an access database. The point is I
created the database in Access 2000 and connected to the databse using
Microsoft Jet OLEDB 4.0 Provider. But then I came to know that the
Client had only Access 97 so I converted my Database using the
Database utility in Access 2000 to convert to Prior version of Access
and changed the provider to Microsoft Jet OLEDB 3.51.Now when I
try to create the installation program using Package & Deployment
Wizard it shows me that there are no dependencies for MSADO20.tlb.
If I still continue the setup program and try to install it on a
machine having Access 97 it gives me an error saying
"Specified Provider not found". The error number is 3706. This
happens even when I install MDAC_TYPE.exe before installing my Package
onto the client machine. Anyone knowing the answer please help me out.
mangeshlAsked:
Who is Participating?
 
lpsharmaConnect With a Mentor Commented:

Installation of ADO 2.0 makes an entry into the regisrtry for provider 3.51.
"Microsoft Jet OLEDB 3.51"
MSADO20.dll

Where as installing ADO 2.1 will make an entry of provider 4.0
"Microsoft Jet OLEDB 4.0"
MSADO15.dll

Please check provider which you have suplied in the program and simultaneously check this entry into the registry. If it is missing you need to install the appropriate ADO

Provider information should be in the registry.

This you need to take care on the machine on which you are going to deploy the application ....
0
 
Éric MoreauSenior .Net ConsultantCommented:
Continue to use Microsoft Jet OLEDB 4.0 even with Access 97 database.
0
 
mangeshlAuthor Commented:
It still does not working.
0
 
sal2000Commented:
Recently I ran into this same problem. What I did was, while in Access 2000, I converted the database to 97 (using the Database utility) and converted my progam to an odbc connection with it pointing to a dsn which points to my database.
There is a way around it but you supposedly have to load the new mdac but it could possibly mess up any access applications they may have and there was also a problem where the new version of mdac didn't provide some drivers that the previous version did.  I had found the information on Microsoft's web site when I was looking for something else. It was just easier to go with ODBC then fight Jet 4.0
0
All Courses

From novice to tech pro — start learning today.