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

Klaus, yes, "runtime detection" in thismanner is not recommended. LV 2009 keeps the folders of the modules in the executable, so this approach does not work anymore in LV 2009.Either you move the VI in the rootfolder of your toplevel VI (so two folders up \RFbeam_DT1\DT1_LabVIEW ) or use the call chain approach as Ben uses. hope this helps,Norbert PS: Keeping the setting for the file layout might be a temporary working solution, but i would not recommend you to stick on this.

LabVIEW

Wrong "Current VI's Path" in LV 2009

Solved!

tst wrote:

What about backward compatibility?

Never thought about it, bad mind. Always only "looking fwd to..."

- Partha ( CLD until Oct 2027 🙂 )

Message 31 of 31

(521 Views)

LabVIEW

Wrong "Current VI's Path" in LV 2009

Re: Wrong "Current VI's Path" in LV 2009