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)