Open VI Reference Function and a RUN VI RUN VI Method Causes Error 1000 with version 2014

[aputman]

---

@robojeff wrote:

After some thought, this might not be a LabVIEW 2014/ 2015 issue at all...

It might be a Windows 10 issue and how and what it allows LabVIEW to execute out of memory...

---

It has nothing to do with Windows 10.  If you load up Labview 8.6 and run the application in the IDE, I believe you will get the same error.  But when compiled into an EXE, the code in the false case shown above is deleted from the block diagram because it can never be called.  The compiler is smart enough to know that and in an effort to reduce memory usage and file size, unnecessary code is removed.  Not true in the IDE.  

[robojeff]

---

@aputman wrote:

---

@robojeff wrote:

After some thought, this might not be a LabVIEW 2014/ 2015 issue at all...

It might be a Windows 10 issue and how and what it allows LabVIEW to execute out of memory...

---

It has nothing to do with Windows 10.  If you load up Labview 8.6 and run the application in the IDE, I believe you will get the same error.  But when compiled into an EXE, the code in the false case shown above is deleted from the block diagram because it can never be called.  The compiler is smart enough to know that and in an effort to reduce memory usage and file size, unnecessary code is removed.  Not true in the IDE.  

---

Actually, when I run the Labview V8.6 IDE on a non Windows 10 system this works just fine but if I use Labview 2014 or 2015 IDE on a windows 10 system it fails every time.

Also, the LabVIEW v8.6 compiled EXE works just fine on a Windows 10 PC but the 2014 Compiled exe errors out just like the in the same version IDE, so it must be something to do with Windows 10 and Labview 2014/ 2015...

[rolfk]

---

@robojeff wrote:

---

Also, the LabVIEW v8.6 compiled EXE works just fine on a Windows 10 PC but the 2014 Compiled exe errors out just like the in the same version IDE, so it must be something to do with Windows 10 and Labview 2014/ 2015...

---

The problem with this reasoning is that you change two variables at the same time and then conclude that one of the changes is the problem. It is very unlikely that the underlying OS will have an affect on this level in LabVIEW, but quite likely that the different LabVIEW version could have this effect.

NI generally tries to avoid such functional changes between LabVIEW versions, but sometimes an improvement at some point can have an unexpected effect on a different place. And sometimes changes are necessary to make something work, which cause to disallow something which was never meant to work like that.

[robojeff]

---

@rolfk wrote:

---

@robojeff wrote:

---

Also, the LabVIEW v8.6 compiled EXE works just fine on a Windows 10 PC but the 2014 Compiled exe errors out just like the in the same version IDE, so it must be something to do with Windows 10 and Labview 2014/ 2015...

---

The problem with this reasoning is that you change two variables at the same time and then conclude that one of the changes is the problem. It is very unlikely that the underlying OS will have an affect on this level in LabVIEW, but quite likely that the different LabVIEW version could have this effect.

NI generally tries to avoid such functional changes between LabVIEW versions, but sometimes an improvement at some point can have an unexpected effect on a different place. And sometimes changes are necessary to make something work, which cause to disallow something which was never meant to work like that.

---

OK, thanks for sharing your opinion....