• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 559
  • Last Modified:

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.
0
tinman1412
Asked:
tinman1412
1 Solution
 
lochianoCommented:
Application-defined or object-defined error is a very generalized error in that if the DLL that you are calling does something stupid (as in not knowing what driver to use to see the DB) then that is one of the generalized messages that VB can get back.  There is another error that is inside of the DLL but normally you do not see that.

The first thing that I would do if I was you and that is to see if this is isolated to one PC or is this all over the place.

Next, make sure that the PC is up to date.  For example is this is a Windows 95 box then is DCOM and MDAC up to date?  Have you loaded all of the VB service packs.

If that does not do it then I would try to see if the problem can be reproduced in some other application.  What does Excel do when you try to access the same file?  VB has a good wizard for connecting into ODBC files and that could show you the connect string that it is using.

Try another connection method.  IF CreateObject() is giving you problems, then try creating an  (dim RS as new ADODB.Recordset) ADO object.  If VB does not work and Excel can see the file correctly then use ODBC to go to excel, then to the database.  It will be slow but you can see how it is being done there.

Go into the ODBC manager and drop the name and put it back in.  If the object created is an Oracle object then be sure to make a SQLPlus connection to verify that you can bet to the database in question.

Watch enviroment varables.  You can kill a Oracle session by not having the path statement set correctly.

Bottom line.  There may not be an easy answer to your question.



0
 
jjmartinCommented:
Download Microsofts component checker.  Component Checker checks installed version and diagnoses installation issues with Microsoft Data Access Components.  This should identify and correct your problem.  It is available at:


http://www.microsoft.com/downloads/release.asp?ReleaseID=15754
0
 
lochianoCommented:
I agree that the program offered is very good, but do not overlook a little good common sense.
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
tinman1412Author Commented:
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
0
 
lochianoCommented:
Which version MDAC and did you install or reinstall DCOM95?
0
 
tinman1412Author Commented:
I only installed MDAC version 2.1
0
 
lochianoCommented:
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.

0
 
tinman1412Author Commented:
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
0
 
lochianoCommented:
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.
0
 
tinman1412Author Commented:
If MDAC mess up my other odbc settings, would a newer version of DCOM do the same?
0
 
lochianoCommented:
We have never seen that. DCOM95 seems to be DCOM95.
0
 
JamesADalyCommented:
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
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now