database executable

[Joshua731129]

Hello Everyone,


I recently started using Database Connectivity VI's to connect to a MySQL database. We have everything working great in the development version. However, when I build an executable and deploy it to other machines the executable starts looking for all the sub-vi's that contain any of the VI's from the database connectivity tool set. Why is that? Can you build executables containing these database tools without worrying about them needing access to the actual development vi's? If so, how do you?

Joshua Meyers

[Joshua731129]

I should have also included that I am using Labview 7.1. Also this post was suppose to go to the Labview discussion forums and it says teststand for some reason. I am new, sorry.

Josh

[Philip_Courtois]

Hi Joshua,

When building an executable out of a VI that uses the Database Connectivity Toolkit, you have to add a few other things than just the VI. This is all clearly described in this KnowledgeBase:

Building Stand-Alone Executables With Database Connectivity Toolkit VIs

Let me know if you have any further questions, thanks.

Have Fun!