tinman1412
asked on
ODBC error
I have a Visual Basic application that doesn't work. I use Odbc, file dsn, and an Access Database in the Application.
The error when I try to run is:
Connect: Application-defined or object-defined error. 40002 IM003: Specified driver could not be loaded due to
system error 1157 (Microsoft Access Driver (*.mdb)). D due to system error 1157 (Microsoft Access Driver
(*.mdb)).
Please let me know if you have the anwer, thanks.
The error when I try to run is:
Connect: Application-defined or object-defined error. 40002 IM003: Specified driver could not be loaded due to
system error 1157 (Microsoft Access Driver (*.mdb)). D due to system error 1157 (Microsoft Access Driver
(*.mdb)).
Please let me know if you have the anwer, thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I agree that the program offered is very good, but do not overlook a little good common sense.
ASKER
I've installed a setup that updates the Microsoft Access Components, and it works, but it messes up my odbc setting for other applications. Does anyone know why?
system I'm running this on is Win 95,if this makes a difference
system I'm running this on is Win 95,if this makes a difference
Which version MDAC and did you install or reinstall DCOM95?
ASKER
I only installed MDAC version 2.1
I have seen several issues with MDAC version 1.5 to MDAC version 2.5. Programs run with one or the other but not both.
I am guessing that you have some programs that were compiled with the older version and some that were compiled with the newer copy. If that is the cane then the only solution is to recompile the old stuff using the newer stuff.
I am guessing that you have some programs that were compiled with the older version and some that were compiled with the newer copy. If that is the cane then the only solution is to recompile the old stuff using the newer stuff.
ASKER
Well, I've tested my application on 2 other computers and they both work, it's just one in particular does not and I'm confused as to why.
All 3 computers are win 95
All 3 computers are win 95
We have several hundred VB programs. All of them use MDAC. 3 would not work when we went from 1.5 to 2.15 The operating did not make any difference) From 2.15 to 2.5 we have had not known errors.
We did not persue it much because at the same time we were interesting in making some other changes but I would half to guess it was the version of one of the dependent objects of the MDAC driver that did not like something else.
We did not persue it much because at the same time we were interesting in making some other changes but I would half to guess it was the version of one of the dependent objects of the MDAC driver that did not like something else.
ASKER
If MDAC mess up my other odbc settings, would a newer version of DCOM do the same?
We have never seen that. DCOM95 seems to be DCOM95.
I've been pulling my hair out over a similiar problem. The error that would come up on certain machines during installation of a vb app I had written would be, "specified driver could not be loaded...system error...microsoft access driver.."
In the end we managed to fix it by copying ODBCJT32.dll from a machine the application worked on to the problem machine and this fixed it.
On the problem machine it was version 3.xx and on a machine that worked okay it was 4.xxx
James
In the end we managed to fix it by copying ODBCJT32.dll from a machine the application worked on to the problem machine and this fixed it.
On the problem machine it was version 3.xx and on a machine that worked okay it was 4.xxx
James
http://www.microsoft.com/downloads/release.asp?ReleaseID=15754