LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview 2014 to Labview 2018

Solved!
Go to solution

Hello,

 

I have and executable that needs to be ran on a windows 7 (32bit) LabVIEW 2014 and windows 10 (64) LabView 2018.

 

This issue is there can only be one executable and it needs to work on both stations.

 

Is there any workarounds that can allow my executable to work on both?

 

Thank you!  

0 Kudos
Message 1 of 4
(1,419 Views)
Solution
Accepted by topic author JP4444

If you absolutely need LV2014 on one station and LV2018 on the other, then no, there is no way to run a single EXE on both.

But why you should have such an awkward constraint?

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
Message 2 of 4
(1,397 Views)

Thank you for the quick reply! 

 

The reason for the awkward constrain is that I work with "sold off" software. That once it's done it cant be changed unless we put money into reselling off.

 

 

 

 

0 Kudos
Message 3 of 4
(1,386 Views)

As stated, a LabVIEW 2014 binary must have access to the LabVIEW 2014 run-time engine which is a separate install that contains things needed for the binary.  If you have a system where the LabVIEW 2014 run-time isn't available, then you cannot run any LabVIEW 2014 binaries.  Later versions of LabVIEW do have some forward compatibility in the run-time engine so a LabVIEW 2020 binary, can be loaded in a LabVIEW 2021 run-time.  But there are several other constrains to think about when it comes to other libraries like VISA, DAQmx, XNet, etc.  

0 Kudos
Message 4 of 4
(1,379 Views)