Problems when trying to export VI using save hierarchy

[bigt]

I have a VI I want to send to another engineer at a different location. I know what version of LabVIEW they have, but I do not know if they have all the instrument drivers. I choose 'save hierarchy' to duplicate the VI and all it's dependencies to a seperate directory. It tells me some of my instrument libraries cannot be duplicated because they are already in memory, and asks if I want to rename them. I save the instrument libraries with a new name.

However, I notice the copied VI still links to the instrument libraries in my labview directory. How do I get the copied VI to link to the renamed instrument library?

What is the easiest way to get the VI to my fellow engineer and be sure it will be executable? Make it into an .exe?

[SMeserve]

Hi bigt,

The best way to distribute applications to other users for simply running the code is using an installer.  First you will build an executable then package it in an installer where you can choose other files to install with the executable.

[bigt]

OK, that is what I suspected, and it solves my immediate problem. However, I do have a need to distribute source code for my VI's. It's difficult to send all the source code to someone and assure that all the needed sub VIs and instrument drivers are included. Even when I do make an executable, it sometimes includes instrument drivers in a seperate folder instead of including them inside the .exe

[SMeserve]

Hi bigt,

If you want to distribute code, use a source distribution.  It is another option under Build Specifications.