-
Using ADO and installing a VB6.0 application fresh on someones machine causes this error.
This error has occured for me before and it went away, I don't know precisely what fixed it, but now my friend at another company is getting the same thing and we can't figure it out. I know I had upgraded from MDAC 2.0 to MDAC 2.1 (SP2) but I can't verify that this fixed the problem.
Anyone have the same issue that knows what's going on.
Verified: MDAC version, MDAC is installing on the machine from the Setup program, confirmed a reboot.
-
Try to apply SP3(service pack 3) and upgrade you MDAC. before installing SP3 reinstall first the MDAC. Compile you Applcation. When packaging your App. make sure all component are updated.
crack
-
M$ sucks. They upgrade MDAC without changing the source code wizard in VB6.
You can
1.Change "3.51" to "4.0" in your VB source code.
or 2.install MDAC2.0 in any computer you want to install ur application.
Hao
-
To further clarify lupus' remarks, if your application uses the Microsoft.Jet.OLEDB.3.51 provider in your connection string, you must distribute MDAC version 2.0.
When you install VB 6 SP3, MDAC version 2.1 replaces MDAC version 2.0, and 2.1 only includes drivers for Jet.OLEDB.4.0 (Access 2000 databases). MS seems to be cramming this driver down our throats, because you cannot download MDAC version 2.0 any more from their site. However, you can still download MDAC 2.0 from this site:http://www.integrade.com/downloads/mdac.html
In short, you are distributing the incorrect version of the MDAC.
HTH
Tom
-
mdac 2.1
do you have website to get mdac 2.1?
-
-
MDAC worries
Thank all for your replies. I will send this information off to the client to ensure everything listed here is satisfied.
OTHER SUGGESTIONS ARE WELCOME IN THE MEAN TIME.
You all know what I read today ... and this may be one of the issues ...
Q170163 INFO: VB 6.0 Readme Part 2: Data Access/Databinding Issues
Below is a snippet of the information in the Info Article:
Code:
Setup for Data Access Applications May Fail on Windows 95/98
When redistributing a Visual Basic 6.0 application that includes data
access components, setup will fail if DCOM for Windows 95 and Windows 98
isn't present on Windows 9x client machines.
Here is another interesting article:
Q240377 - HOWTO: Insuring Jet 3.5 Is Installed Correctly (Part I)
