LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

sql toolkit connection troubles on CVI

Solved!
Go to solution

Hi all.

 

I wrote this message because I'm not able to find a solution to the problem decribed above...

 

I developed a program that uses SQL Toolkit, on CVI 9. I access to a MS Access 97 database, using a ODBC connection (DSN=MyProgram).

 

The program works fine, on windows 7, and on windows XP (windows xp is the end-user operating system).

 

However, when I install the program on the end-user pc (windows xp), and after create the DSN user on the ODBC connections, I got an error when executing the program. The error refers to is not possible to connect the database (acrosss the ODBC connection).

 

As I said, on other differente machine, with windows xp, it works!!!!

 

I'm a little bit lost.Do I need some special component installed for making SQL Toolkit work fine???

The PC with XP where the application works, has the same applications instaled than the end-user PC.

 

I tried to install on the end-user pc the LabWindows CVI with SQL Toolkit, and I checked that  when the connection to the DSN is tried, I get "Unknown error".

 

Some help will be very appreciate!!!!!!!

0 Kudos
Message 1 of 6
(4,153 Views)

Hi again.

The connection sentence from SQL Toolkit that doesn't work is the following:

 

dbHandle = DBConnect ("DSN=Test");

 

This one, returns an error, with the asociated string "Unknown error".

 

Should be ADO troubles????. I tried to install MDAC 8.5 on the end-user PC (with XP), and the installation process said that the last revision was installed and there was not necesary to install it.

 

Thanks in advance!

0 Kudos
Message 2 of 6
(4,144 Views)
Solution
Accepted by Falcone
Run it on pc without Sql toolkit, you need to copy the cvidb32.dll to your system32 folder of your windows.
0 Kudos
Message 3 of 6
(4,139 Views)

Of course, I'll check, but I think the installation should copy this file.

 

I have checked the application on three differents PCs with XP and only fails on one of them, the most important....

 

I'll check what you say.

0 Kudos
Message 4 of 6
(4,114 Views)
Hello to everybody 1) It is necessary to verify that the pilot (driver:odbc32.dll, odbccr32.dll, odbcint.dll, odbccp32.dll) ODBC is installed on the PC of your Customer If the pilots are not installed it is necessary absolutely installed the run time MS ACCESS. 2) It is necessary to copy files following one ivlib.dll, ivsql08.dll, ivutl08.dll to your system32 of the machine of your customer
0 Kudos
Message 5 of 6
(4,105 Views)

That was the reason. The file cvidb32.dll was not located on c:\windows\system32. I placed it manually on that location, and the application finally works!!!!

 

Some questions are now pending... I wonder why this dll file, after the installation process, is not installed correctly......

 

Thanks to all for your help.

 

Best regards,

Dani.

0 Kudos
Message 6 of 6
(4,084 Views)