SQL Toolkit for G
For Win 3.1 (16 bit version), Win 95 and NT platforms (32 bit version)
The SQL Toolkit allows users to access and update databases from LabVIEW. LabVIEW interacts with a database through a database driver - the toolkit ships with drivers for many databases such as dBASE and FoxPro. A user is not limited to using the drivers that ship with the SQL Toolkit. For instance, if they already have Excel, they should configure their database to use the Microsoft supplied Excel driver. The SQL Toolkit establishes a database connection based upon information stored in the ODBC Administrator. ODBC is a database standard that specifies connectivity between database vendors. The ODBC Administrator is a Microsoft Utility that ships with the SQL Toolkit. It is also installed with other Microsoft Programs such as Excel or Access. The ODBC Administrator keeps track of databases through their DSN - data source name. Additional connection parameters (user name and password) and database attributes such as file cache size and locking can be specified in the ODBC Administrator also. All a user needs to do to connect to a properly configured database is specify the DSN to the Connect.vi in LabVIEW. Once a connection is established, SQL statements can be executed on the database through the SQL vi's.
Error 100 - Dll Setup Error. Could not load qelib.dll
This error indicates that the SQL Toolkit was not properly installed. The toolkit must be installed on the development machine and each target machine that the executable runs on. There are notes below for installing a runtime version of the Toolkit for development distribution.
I can't connect to a database.
If the Connect.vi always returns with an error, make sure that the database is properly configured and that the DSN is specified in the block diagram exactly the same way that is appears in the ODBC administrator. An alternative way to connect to a database is by wiring a true to the dialog input of the Connect.vi. Instead of specifying a DSN, a dialog box will appear that lists the available DSN's in the ODBC administrator, and lets the user choose one.
The examples won't work.
Some customers try to run the SQL examples for dBASE and specify another DSN for a different database. The examples might not work with any other database driver, due to syntax differences between the different databases.
Why do I have to buy a license for applications that I distribute?
National Instruments licenses the database drivers from Intersolv, and pays the licensing fees for the use of the drivers during the development phase. If you are distributing applications, then you must pay a license fee for each driver and each person who will use the database. There are single user and multi-user licenses, with single or multiple databases (connecting to dBase and FoxPro databases within the application would require a multi-database license).
If you are not using any of the Intersolv drivers, then there is no license fee. It is still beneficial to perform an expert install of the SQL Toolkit on the target machine because there are ODBC Interface drivers that LV uses to call the database dll's.
How to install the runtime version (or do an expert install)?
Installing the runtime version and license for the SQL Toolkit is equivalent to performing an Expert install, so these instructions apply to both. An expert install allows you to install drivers and/or the ODBC Administrator and Interface files. It is not necessary to have LV installed. Due to an oversite, the 2.0 version of the toolkit must be installed in the same directory as LabVIEW.exe. So, create a file named LabVIEW.exe and point the installer to that directory. Deselect the SQL Toolkit VI Libraries and Application Examples. Nothing will be installed into the chosen directory. All drivers are installed in the Windows\System directory. Choose the desired drivers and ODBC files, and finish the installation.