LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

ODBC - Error: Could not load the automation support DLL

Hello,
I am using CVI 5.5 dev environment, with the 6.0 sql toolkit loaded and using WinXP. The function DBConnect("CONNECTION_STRING") returns "Automation error code -11, Could not load the automation support DLL". My PC is configured correctly, as far as I can tell, with an OpenLink database. Start->Settings->ControlPanel->AdministrationTools->DataSources(ODBC)->System DSN shows that the OpenLink driver is there, and named MFGPRO_database. Its configuration dialog provides a "test Connection" button, that when pressed indicates a successful connection. I believe all I should do to successfully connect is to use the MFGPRO_database as the argument, i.e. stat=DBConnect("MFGPRO_database"). One other note: The only dll I can find (using regedit find) associated with this database name (MFGPRO_database) is c:\programFiles\OpenLink\olod4032.dll. I wondered if copying this dll to the system directory (winnt\system32) would work, it did not, same results.
Anyone have an idea?
0 Kudos
Message 1 of 3
(3,895 Views)
Are you still having problems with this?

I've documented this procedure for myself as I always forget how to do it myself.

See my reference page on: http://www.jattie.co.uk/software/cvi/help/sqlstring.htm

Best regards

Jattie van der Linde
Jattie van der Linde
Engineering Manager, Software & Automation
TEL Magnetic Solutions Ltd
0 Kudos
Message 2 of 3
(3,871 Views)
The problem still exists, but I have discovered that the cause is a general incompatibility between the CVI5.5 development environment and the CVI7.1 runtime engine, when using the SQL toolkit. I get a first chance exception fault once for each SQL toolkit library call I make. If I keep hitting the continue button on the error pop-up, it eventually comes out with all of the query information. This behavior only occurs during runtime of a debug executable. Release executables work fine, even if built with the older dev environment on a new runtime engine. Now that I am aware of the incompatibilities, I will just navigate clear.

Thanks
0 Kudos
Message 3 of 3
(3,861 Views)