LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Wrong "Current VI's Path" in LV 2009

Solved!
Go to solution

Same program built with application builder works in LabVIEW8.2.1, but does not work in LV2009.An example is included in the attachment.

The VI "Current VI'2 Path" returns correctly in development environment:

 

F😕Projekte\LabVIEW\Test_2009\EvaluateProgramPath.vi

 

If run as exe built in LV2009 (and also built as installer), it returns an unusable output:

 

F😕Projekte\LabVIEW\Test_2009\builds\EvaluateProgramPath.exe\EvaluateProgramPath.vi

 

In LV8.2.1 and all earlier versions, the *.exe returned exactly, where the *.exe resides.

Many of our existing LV programs depending on this VI can't be migrated to LabVIEW2009.
Does somebody know a solution or patch without changing existing sources?

Thanks for any tip.

Klaus 

 

 

Message Edited by Mezger on 08-25-2009 06:31 AM
0 Kudos
Message 1 of 31
(4,458 Views)

Check this thread. There have been some changes, but there seems to be an option in the installer to use the legacy file layout.

 

Daniel

 

Message 2 of 31
(4,447 Views)

Hi Klaus,

sorry, but i don't see the problem. For me it seems correct.

 

Mike

Message 3 of 31
(4,444 Views)

@dan_u

Thanks, I tried the switch "LV8.x file layout" but it did not change anything.

 

Klaus

0 Kudos
Message 4 of 31
(4,430 Views)

Actually I agree with Mike, the output you see (both for compiled and VI) is what I would expect in 8.5 (don't have 8.2, but I guess it behaves the same) as well.

 

Daniel

 

Message 5 of 31
(4,427 Views)

Mike,

The problem is, that the *.exe filename is followed by the *.vi in the path output.

In LV8.x there was the path to the *.exe only, what also made sense.

I believe, that the new output is the result of a bug, because it does not carry a useful information and is not compatible with all the earlier LV versions.

 

Thanks anyway for your immediate responses!

 

Klaus

0 Kudos
Message 6 of 31
(4,426 Views)

Mezger wrote:

...

In LV8.x there was the path to the *.exe only, what also made sense.

...

Klaus


Maybe in a parallel dimension but NOT in any time and space that I have been in.

 

I have a a re-use VI that I have been using since LV 6.0 to resolve the differences in paths between the development and exe environments. i see no difference or bug.

 

Ben

 

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 7 of 31
(4,417 Views)

Hi Klaus,

afaik, there is no change. The path was also in a LV7.1 application like this: "dir\exename.exe\viname.vi".

 

Mike

Message Edited by MikeS81 on 08-25-2009 02:08 PM
0 Kudos
Message 8 of 31
(4,417 Views)

Mezger wrote:
The problem is, that the *.exe filename is followed by the *.vi in the path output.

That's how it should be. Also in LV 8.x.

 

Daniel

 

0 Kudos
Message 9 of 31
(4,414 Views)
Every version I've used going back to 3.0 displays the paths exactly like 2009.
Message 10 of 31
(4,409 Views)