Strange current VI`s path returned in standalone application

[Gunnar_Kulbotten]

I know that there is a difference in the path returned when using the "Current VIs path" in the development environment and in a standalone application, but this is not what I had expected: This is the path returned from the Current VIs path in the standalone application:

C:\LabView-programmer\RADHAZ-programmer\RADHAZ\builds\rad.exe\RADHAZ-programmer\RADHAZ\rad.vi. Why is this the correct path to the VI?

If I strip this path once, and build a new path with the name of my dynamically called VI  I get: C:\LabView-programmer\RADHAZ-programmer\RADHAZ\builds\rad.exe\RADHAZ-programmer\RADHAZ\instr.vi. It starts from this path, but It won`t load some text-files located at C:\LabView-programmer\RADHAZ-programmer\RADHAZ\builds\kal-data without making changes to the instr.vi.

I tried to used the App.Dir property to find the correct top level directory, and it returns C:\LabView-programmer\RADHAZ-programmer\RADHAZ\builds as expected. But this is not the path that the dynamically called VI need.

Any suggestions is appreciated..

I searched for a detailed tutorial for setting up the build specification, but didn`t find any that helped much.

Gunnar

[GerdW · Accepted solution]

HI Gunnar,

have you tried the last point of the Advanced AppBuild settings as described in the help?

[tgwowgt]

Thanks GerdW this solve for me!

But why this behavior? What kind of logic behind the strange path returned? In my understanding, nothing should be simple of a costant returning a path... This one seems out of control, i'm temted to make one myself...

[EspenR]

Hi

For a little more explanation take a look at this KB

Basically when you create an .exe file you get an extra folder.

Reagards

Espen

[Gunnar_Kulbotten]

I used GerdW`s advice (advanced settings"Use LabVIEW 8.x file layout"), problem solved!

Gunnar