Oralce unable to load sqresus.dll

[Julian Shelbourne]

Hi, I think I have the solution to this problem:

MFC42.DLL: The Microsoft module, MFC42.DLL version 4.21.0.7303,
may not work with some of the Oracle ODBC Drivers.
The following error message may be produced by the
when trying to connect to a data source from the ODBC
scanner that is using version 8.1.6.4, 8.1.78.0, or
9.00.11.00 of the Oracle ODBC Driver:

"Error: Cannot load Resource File sqresus.dll"

Clicking on OK button may also cause the following
error message to be produced by the ODBC scanner:

"Data Source connection test failed with the
following error:

Specified driver could not be loaded due to
system error 1114 (Oracle in OraHome81)."

Probably, your application has MFC42.DLL somewhere in its directory structure. To fix the problem, simply go to WINNT\System32 (or the Windows directory for the Windows OS you're using) and copy MFC42.DLL from there into the directory of your application where your current (old) version of MFC42.DLL is currently resident (over-write the old version - or re-name it first). Your application should work correctly after that (no reboot required).

Julian

>There are several threads to be found relating to this Oracle ODBC
>error, "unable to load sqresus.dll", but I have not found them
>particularly useful. Especially on Metalink (Oracle's MSDN), all they
>say is "put the file first in your path".
>
>Facts:
>VB 6.0 latest DAO ref lib
>ActiveX DLL project
>Oracle 8.1.7.6.0 ODBC Driver
>MDAC latest 2.6 release
>ORACLE_HOME/bin is most definitely in the path
>
>DSN created and working fine in every other application. I can use
>MSAccess to link to Oracle tables and all is well. It is only when I
>attempt to run the ActiveX app that it fails. From within the
>ActiveX, I have displayed the contents of the path, using "environ"
>function, and it is what I expect, with the oracle bin directory
>leading the way.
>
>I suspect it may have something to do with threading compatibilities
>and am hoping someone much smarter than myself can shed some light.
>
>Could it also be that a called ActiveX DLL does not share the same
>path as the system?

Message sent from http://www.aewnet.com