03-24-2022 10:13 AM - edited 03-24-2022 11:08 AM
I have made a connection via IP across the network with MySQL Workbench on both machines and been able to input information into my DB and subsequent tables without issue. But when using when trying to connect with LV that is when the troubles persist.
Blog for (mostly LabVIEW) programmers: Tips And Tricks
03-24-2022 10:53 AM
@Coddiwomple wrote:
I have made a connection via IP across the network with MySQL Workbench on both machines and been able to input information into my DB and subsequent tables without issue. But when using when trying to connect with LV that the troubles persist.
Maybe start LabVIEW as an administrator? (That's not the same as having admin rights as a user, you might need elevated rights).
03-25-2022 02:27 PM
At the end of the day, I chose to go through and wipe all my installations of MySQL and it's subsequent pieces to review what could have gone wrong. Once re installed I was able to connect via UDL using a MySQL ODBC connector to a host computer running Win7. Then ran it in reverse to connect from Win7 as client to a server running on my WIN10. Then found an error. The SSL was causing an unknown error at the connector. I tried updating internet time across the network to ensure we were all jiving appropriately. And then I came across an update to the newest version of MySQL ODBC connectors that had finally been made available in 32 bit for Windows. I uninstalled my previous driver from the host computer and lo and behold, I created a successful System DSN which plugged seamlessly into my datalink, using LV18 and DB toolkit 18. It communicated perfectly with MySQL server and transferred data back and forth. SO WOOOOT!
Now to actually begin creating an inventory management system that will work for our client, hahahaha.
Thank you ALL for your replies. I appreciate every single one of you for your helpful insight.
Blog for (mostly LabVIEW) programmers: Tips And Tricks