I used this toolkit in one of my projects to record the test results of UUTs into MS Access database. I created a save results to database subVI with this toolkit. The subVI looks like this:

It is simple. When the table does not exist, this subVI creates the table and inserts data, when the table exist, the subVI inserts data only. When I call this subVI for the first time, everything is fine. But when I call it again with the same table name and different data especially when the string data in the same column is much longer than the last time, there will be an error. After checked the Access database, I found out that the DB Tools Insert Data VI created the table and formatted every column’s size exactly the same as the initial data set. So, inserting data that longer than the initial will make an error.

The solution is first check if the table exists, then use the DB Tools Create Table VI to create table if table does not exist as in the following diagram:

Related Posts

• January 16, 2009 -- Access Different Access Database Files Programmatically in LabVIEW with Database Connectivity Toolset (2)
• July 10, 2009 -- Move Up and Down Tree Control Sub-items Programmatically in LabVIEW (0)
• April 20, 2009 -- Transfer More Than Text Message in Queue Between Loops in LabVIEW (2)
• March 16, 2009 -- How to Create Linked List in LabVIEW (0)
• February 22, 2009 -- Build a Tri-State LED Indicator in LabVIEW (0)
• February 16, 2009 -- NI Announcing the LabVIEW 2009 Platform Beta Program (0)
• February 2, 2009 -- A Strange Problem When Calling External DLL with LabVIEW (0)
• January 13, 2009 -- A Way to Improve User Experience in Complicated Applications in LabVIEW (5)

To change the UDL file’s content in LabVIEW programmly is not easy too. Because UDL file  is unicode-formatted, and LabVIEW is quite limited in support to unicode. I had tried several ways to change the database file name in UDL file and save the UDL file to hard disk. And when I open the changed UDL again, I got “File corrupted” message. It seemed that it is not a good way.At last, I had to read the help file of Database Connectivity Toolset word by word to find a way to work round. Wow, I found out that the VI DB Tools Open Connection is a Polymorphic VI that accepts string and file path data types. Just append the Access database file’s path after “Provider=Microsoft.Jet.OLEDB.4.0; Data Source=”, and wire it to connection information connector of DB Tools Open Connection VI, and everything will be OK.  Everything get solved.

It is really a good habit to read the help file carefully.

Related Posts

• March 8, 2009 -- A Note about Using Database Connectivity Toolset in LabVIEW (0)
• December 24, 2008 -- Howto: Creating a Microsoft Data Link file (.UDL) for Connecting to Microsoft Access in LabVIEW (0)
• December 18, 2008 -- How to write and read Access database in LabVIEW (0)
• July 10, 2009 -- Move Up and Down Tree Control Sub-items Programmatically in LabVIEW (0)
• April 20, 2009 -- Transfer More Than Text Message in Queue Between Loops in LabVIEW (2)
• March 16, 2009 -- How to Create Linked List in LabVIEW (0)
• February 22, 2009 -- Build a Tri-State LED Indicator in LabVIEW (0)
• February 16, 2009 -- NI Announcing the LabVIEW 2009 Platform Beta Program (0)