Common Questions: LabVIEW SQL Toolkit
Primary Software: LabVIEW Toolkits>>Enterprise Connectivity Toolset
Primary Software Version: N/A
Primary Software Fixed Version: N/A
Secondary Software: N/A
Problem: This document gives a general overview on the LabVIEW SQL Toolkit version 5.0 and also answers some common questions relating to the toolkit. The overview and troubleshooting tips in this KnowledgeBase document, however, are applicable for all versions of the SQL Toolkit.
Solution: The LabVIEW 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. You are not limited to using the drivers that ship with the SQL Toolkit. For instance, if you already have Excel, then you should configure the 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 Data Source Name (DSN). Additional connection parameters (user name and password) and database attributes such as file cache size and locking can be specified in the ODBC Administrator as well. The user simply needs to connect to a properly configured database and specify the DSN with the Connect VI in LabVIEW. Once a connection is established, SQL statements can be executed on the database through the SQL VIs.
LabVIEW SQL Toolkit Troubleshooting Tips
- 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.
- Cannot 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 DSNs in the ODBC administrator, and subsequently allows the user to choose one.
- Examples will Not 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. Make sure that the syntax in your program is correct for the database you are using.
- Purchasing a License for Applications that You 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 using the database. There are single-user and multi-user licenses, with single or multiple databases (connecting to different databases within the same 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 LabVIEW uses to call the database DLLs.
- Installing the Runtime Version (Performing 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 LabVIEW installed. Due to an oversight, the 2.0 version of the SQL Toolkit must be installed in the same directory as LabVIEW. Thus, you must create a file named LabVIEW.exe (a simple text file with a .exe extension will work), and point the installer to the directory in which that file resides. Then you can deselect the SQL Toolkit VI Libraries and Application Examples. Nothing will be installed into the chosen directory since all drivers are installed in theWindows\System directory. At this point you can choose the desired drivers and ODBC files, and complete the installation.
Please refer to the related links below for more information on using the LabVIEW SQL Toolkit.
Note: National Instruments has replaced the LabVIEW SQL Toolkit with the
LabVIEW Database Connectivity Toolkit. The LabVIEW Database Connectivity Toolkit offers many new features and extended capabilities such as connectivity to most popular databases through Microsoft ADO technology, complete SQL Functionality, and the ability to save records in XML format. If you are considering upgrading your LabVIEW SQL Toolkit we encourage you to consider the LabVIEW Database Connectivity Toolkit.
Related Links: Products and Services: LabVIEW Database Connectivity ToolkitDevelolper Zone Tutorial: SQL Toolkit for LabVIEWProduct Reference: SQL Toolkit for G Reference ManualKnowledgeBase 3QNAD8RX: What Version of a LabVIEW Toolkit Do I Have?
Attachments:
Report Date: 03/20/2001
Last Updated: 09/08/2007
Document ID: 27JCLTDM
