I have a programming computer that has several versions of LabVIEW installed. Once I finish a program, I move the program to the "target" computer (or touch screen) that have only one version installed. The problem I have is when I run a VI, the VI always loads the version of LabVIEW that was used last. When the VI is saved, it compiles to that version and will no longer work on the "target" computer. It seems that saving for a previous version of LabVIEW does not always work (it may be related to going from Win 7 to Win XP). Is there a way to force the VI to open the version of LabVIEW that the VI was compiled with?

@metzler wrote:The problem still exists if you don't know the version of LV that the "target" computer runs.Your targets should not be actually running LabVIEW. They should be running an executable that you build (preferrably with an installer). Then this becomes less of an issue and you have the bonus of not needing LabVIEW licenses for all of your target computers (RunTime Engine is free to distribute).

LabVIEW

Force vi to open compiled version of LabVIEW (not last used version)

Solved!

Author

I don't have the problem of someone changing something on the VI, because I am the only one that programs the VIs. I will try to get some of the targets to run executables.

Thanks for the advice and responses.

metzler CLAD

Message 11 of 11

(713 Views)

LabVIEW

Force vi to open compiled version of LabVIEW (not last used version)

Re: Force vi to open compiled version of LabVIEW (not last used version)