From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
11-23-2006 08:44 AM
Solved! Go to Solution.
11-23-2006 02:14 PM
11-23-2006 02:24 PM
11-23-2006 03:42 PM
How about this?
@RobC wrote:
Unfortunately, I am a student currently using the Student Edition of LabVIEW, and without the means to purchase the toolset you recommend.
11-23-2006 09:27 PM
11-24-2006 02:11 AM
11-24-2006 02:21 AM
11-24-2006 02:23 AM
11-24-2006 04:34 AM
12-22-2006 05:07 PM
One thing to bare in mind is that you do not HAVE to create a DSN connection in the 'Data Sources (ODBC)' section of the Administrative Tools.
You can actually just wire the appropriate connection string to the 'DB Connect' VI. I do this my self because it allows me to easily install applications without having to manually create a DSN in windows . It also means that if I load the connection string from a file, I can easily change the database to read by just editing the INI file..
My connection script is as follows (tested with LabSQL - and the NI connectivity toolkit) ......
DRIVER=MySQL ODBC 3.51 Driver; DB=<Schema Name>; server=<pc name or IP Address>; UID=<username>; PWD=<password>; OPTION=785