Setting up Teststand and MySQL

[TondelliM]

Hi inniwhoni,

thank you for the answer.

Below some screenshots of the process I used to create the connection string with the "Build.." button.

First I created, and successfully tested, an ODBC data source, using Windows administrative tools.

Then I just follow the wizard from TestStand.

The result string let me show the database structure, with all tables and fields, but it does not allow me to view the stored recors (see my previous post).

I'm not sure if this is actually the correct procedure to configure the connection string, but the wizard is quite straightforward and I think I used it as supposed.

[RoxtheFox]

Hi TondelliM,

I did verify that what you are seeing is a bug. You are following the right procedue, but there is a mismatch in TestStand with the connection string that is created in the database options dialog and the one created in Data Link Properties Connection dialog. I filed a bug report for this, CAR 688420.

Thanks for bringing it to our attention. 

[TRJ]

Hi TondelliM,

The Data Link Properties dialog should only** be used to configure connection strings when you want to use an Ole DB provider to connect to the database. Though the dialog (a standard Microsoft utility) allows you to choose an ODBC driver, it adds a layer above it, the Microsoft Ole DB provider for ODBC drivers (MSDASQL) (refer to the final connection string that was created). This is expected behavior for this utility.

There is a known issue with using MSDASQL when using Database Viewer. Please refer to this help topic for more information. So NI recommends that you create the connection strings based on the format provided in this link (mentioned in one of the previous answers), especially if you're using an ODBC driver to connect to the database.

The Data Link Properties dialog can be used to generate connection strings when using Ole DB providers rather than ODBC drivers.

While this information is documented in some help topics, we have filed CAR 723990 to ensure all relevant help topics are updated to call this out explicitly.

**While there is nothing technically incorrect with using the Data Link Properties dialog to create a connection string using an ODBC driver, users need to be aware such connections will add an additional layer to the stack (it will go through the MSDASQL provider first), can be more error prone than directly using an ODBC connection and MSDASQL will not work with Database Viewer as mentioned above.

Regards,

Tinu

[TRJ]

Hi RoxtheFox,

This is expected behavior for the Data Link Properties dialog which is used to create connection strings that use Ole DB providers (see help for Data Link Properties).

So even if users choose an ODBC driver in the dialog, the final connection string will have MSDASQL (Microsoft Ole DB provider for ODBC drivers) added to it. This is why the connection string specified inside the dialog and in the TestStand database options dialog differ for this particular case.

Regards,

Tinu