LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem building exe with dynamic vi

Hi Jeff, thanks for clearing my name Smiley Wink

Yes, it was the path. Managed to resolve it. But it's strange though, why is it does the path have problems when it was working perfectly during VI development? Is it some kind of bug of something during exe conversion?
0 Kudos
Message 11 of 14
(816 Views)
relative paths are different in exes since there is an additional level of path stripping for the exe.  Not a bug but something to remember when building an exe.
 
 
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
Message 12 of 14
(813 Views)
This is a common problem that has been solved in a number of ways.  My favorite way is to create a VI which resides in the directory of the dynamic VIs.  This VI is called statically by the main program.  It only returns its location; I use the current VI path primitive and strip it once.  Dynamic VI paths are constructed relative to the static VI path.  When you build your executable, make sure the statically called VI is placed in the same location as the dynamic VIs.  Then your code will work in both cases with no further attention.
0 Kudos
Message 13 of 14
(795 Views)
Thanks for the tip DF, i'll try that.
0 Kudos
Message 14 of 14
(783 Views)