mangeshl
asked on
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.
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.
Éric Moreau
Continue to use Microsoft Jet OLEDB 4.0 even with Access 97 database.
ASKER
It still does not working.
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.