Find running LV instance version

[Kousy]

If try to open LV12 vi in LV9, it warns File version is later than current LV version. I would like to warn same way when try to open LV9 when LV12 instance is already running. That is Trying to open file in later version - continue , discard? What is the vi should I use to create a warning like this?

[Freelance_LV]

Hi

you can use the property node for Application. select version number property of application and get the version number of current application which is running.

bt, i am not sure what you want to acheive. how do yo plan to use this information?

[Kousy]

Both LV9, LV12 installled on the same machine.

Yesterday I last worked on LV9 project and shut down the system.

Today morning I tried to launch LV12 project and work. It warns File version is later than current version along with Getting started window of LV9.

This is OK scenario. I understand LV9 cannot open LV12 files. So I launched LV12 and opened the project again. No Issues.

In mid of the day if I have some issues reported and try to correct the LV9 project files, hastenly if I opened the LV9 project and corrected and saved, built EXE and sent to client where My client system have LV9 run-time installed only. There is an issue.

If suppose LV warns that you are trying to open the Older version file in Newer version then I will get alerted and launch LV9 and open the project , do corrections, build EXE and I will send safe, right.

That is why I wished to warn this way "when try to open LV9 when LV12 instance is already running. Trying to open file in later version - continue , discard?"

Hope that my issue is clear now. 

Thanks,

Kousy

[GerdW]

Hi Kousy,

right now you get a warning, when you save your VIs with a more recent LabVIEW version!

As it also tries to save the full hierarchy it will tell you why it tries to do that: due to recompiling all those subVIs...

[Kousy]

Dear GerdW,

Yes, you are right. I forget Im getting warning actually. So I should be cautious while saving.

Thanks.

[rolfk]

There are several tools that can help you manage this a little more elegantly when opening VI files from the Explorer.

The LavaG forum has a thread about a possible tools, although it's commercial and their store seems not currently available here.

Two Open source solution exists too on LavaG here and here. It could certainly be extended with many extra features if you want.