11-06-2007 01:41 PM
11-07-2007 02:09 PM
I believe that the KnowledgeBase article linked below will be very helpful. It does not include an example, but it includes an image of a block diagram that could be added to your VI. Please let me know if this is what you are looking for.
Accessing a VI's Current Directory From LabVIEW and a Stand-Alone Application
Meghan M.
11-08-2007 09:19 AM
Yes thank you for that article and yes it is helpful.
I am also interested in any "tricks of the trade" along these lines.
For example My APP is fairly large and I want to make sure that it can find the files and VI's it needs when it is compiled.
I d rather use relative paths to insure that there is no hardcoded path information in the exe which could
throw things off. For example should someone decide to install the executable in a different directory than the intended
"..\APPNAME" the application should be able to sort it out and find what it needs in the subfolders and should be able to do this
in edit mode or executable. I am looking for any techniques and examples along those lines that would make robust and generic handling of paths to the needed resources.
Thank You
11-12-2007 09:59 AM