05-10-2014 05:37 AM
I use labview2013. I programmed some VIs that are put into several folder, and some VI need invoke other VIs in the other folders. The program runs well when debugging, but after I create .exe files, the program prompt that some files invoked can not be found while other files can be found and run well. It's also weird that deffrent computers appear deffrent, files that can not be invoked on one computer can be invoked on another computer.
05-10-2014 07:42 AM
You issues seems to be relative path one, ensure the relative path between source code and executable is same. Relative path of the caller VI and Callee VI changes when converting to executable depends on your folder structure.
05-12-2014 07:07 AM
Since it sounds like you are dynamically loading VIs, you need to make sure you include those VIs in the executable (part ofthe EXE build specification).
Otherwise, make sure you are use relative paths to call your VIs (ie, based on "Current VI's Path").
05-12-2014 08:58 AM
Apart from the already mentioned case (you need to ensure files are in the build) it could also be a lack of packages on the other computers, as VISA if using serial communication, which'd explain why different computers react differently.
/Y
05-12-2014 09:07 PM
Thank you all for reply. Acturally the main vi calls the other VIs dynamically and all these callees are included in the project. Now what concerns me is that the callees also include some drivers supplied by the third party which I could find in the dependencies, but I'm not sure whether the drivers invoke some other .dll or other lib which is not included in the dependency. Have you had problems like this?
05-13-2014 06:54 AM
If you force the VIs to be in the build, then any dependencies should also be included.