10-28-2022 03:21 PM
I work in a factory with older MySQL (5.2, 5.3) servers on site, to enable me to make Database enabled VI's I decided to download MySQL (current -8.0.31.0) and install it on my PC after I cloned some tables to the new server via HeidiSQL I proceeded to try out:
Solved! Go to Solution.
10-29-2022 12:12 PM
In the past the NI DB Toolkit had some quirks and ugly issues and I never used it. I'm also not familiar with those .udl files, because most time I'm using direct connection strings or .dns files.
Your problem sounds like a general issue. If you don't specified a database (schema), then MySQL returns an empty list of tables and no error message. This is correct behavior. Either specify the database within the .udl file or execute a USE sql statement.
10-31-2022 08:48 AM - edited 10-31-2022 08:49 AM
@Martin_Henz Thank you for telling me about the DNS files I followed the instructions from [NI Knowledge] Create a DSN File to Use With LabVIEW Database Connectivity Toolkit and was successful in connecting
In essence making a File DSN instead of a User/System DSN and skipping step two
11-01-2022 03:32 AM
That sounds like a 64/32 bit problem. When you use 32-bit LabVIE you also need to use the 32-bit ODBC Manager to setup DSNs. The ODBC manager in Control Panels refers however to the 64-bit version on 64-bit Windows. You need to launch the one located in <Windows>\SysWOW64.to setup 32-bit ODBC DSNs.