LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

SQL query generated by Insert Data/Update Data vi's?

Solved!
Go to solution

You should be able to use the same connection string as for the DCT. How are you defining the connection with it?

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 11 of 13
(560 Views)

In the DCT I just use the Data Source name ('BurnIn' to be specific) as a Connection Information, but it doesn't work that way with your drivers.

 

Actually if I provide the Data Source name to your drivers they work exactly the same way as with the connection string mentioned above. I still can open only dBase4 tables with short names and can't open neither dBase7 files nor long-named dBase4 files.

0 Kudos
Message 12 of 13
(557 Views)

Mike, all these long - short name stuff and formats probably have something to do with different versions of ODBC configuration in my system, and nothing with your drivers, so thank you again. It is likely that if I'll be able to remove all extra configs your drivers will work well for me.

0 Kudos
Message 13 of 13
(545 Views)