Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Hi Dan_U,
I've attached the block diagram for the section that is opening the .vit. It is interesting to note that if I move a copy of the .vit into the folder of the built executable, the exe appears to open that .vit (but with errors).
All,
I changed my .vits over to reentrant vis, and observed the same problem. After lots of path fiddling, I finally ran across this document, and I'm happy (and also cranky 
) to say that it fixed the build issue with not just the reentrant vis, but the .vits as well!
I am still trying to understand exactly what this means (i.e. if my main executable is located in build/main.exe, exactly what path am I supposed to point to for the .vit), but am satisfied to be able to run the vi independant of developer.
Many, many thanks to those that contributed. As always, it has been a pleasure!
Jim
If you are using a static VI reference it doesn't matter where on disk (or in the EXE) that the VI is. You can get the VI Name (or path) and use that to open the reference. This is a more robust way of getting a reference to the VI. Attatched is the edit of Launch N Folder posted earlier.
