Exec.State shows VI is "BAD", but VI is "GOOD"

[BillMe]

Any reasons why EXEC.STATE would indicate a "BAD" VI, but when opening the VI manually, it runs without a problem? I'm simply opening an App reference then the VI reference (both without error), then using the EXEC.STATE property. It SHOULD show "IDLE" when first loaded (until I use the RUN VI method). (This was something that used to work, but has suddenly changed in it's behaviour).

BillM

[mikeporter]

What happened about the same time that this VI stopped working?
What does the VI that you're trying to run do?
I also wasn't clear, is this a built application or one that you're running under the development system?
What version of LV?
What OS?

Mike...

[BillMe]

What happened about the same time that this VI stopped working?
Nothing changed with the VI calling the dynamic VI. The dynamic VI was changed and runs fine manually. I simply want my MMI to call it instead.
What does the VI that you're trying to run do?
They dynamic VI is a timed loop that writes a bunch of data to shared variables that are bound to my MMI indicators.
I also wasn't clear, is this a built application or one that you're running under the development system?
Development system
What version of LV?
8.2.1
What OS?
XP SP2

BillM

[mikeporter]

Modify your code such that it opens the dynamic VI's front panel and see if the arrow comes up broken. If it is it should tell you what's wrong.

Mike...

[altenbach]

---

@Bill@NGC wrote:
Any reasons why EXEC.STATE would indicate a "BAD" VI, but when opening the VI manually, it runs without a problem?

---

Please open the VI manually once more, then go to "VI Properties...General...list unsaved changes". Anything interersting?

[mikeporter]

I just had another thought. I bet that you have a duplicated VI filename. One version of the VI has a connector pane that is linked to the dynamic VI. A second version has the same name, but a different connector pane, and is used in the VI that calls the dynamic VI. As long as you open the dynamic VI by itself it links to the correct one. Open it dynamically and the dynamic VI finds the version that is already loaded into memory by the caller VI, which breaks the dynamic VI.

Mike...

Message Edited by mikeporter on 07-01-2007 06:30 PM

[BillMe]

Wow, I changed the string display property which contains the name of my VI and lo and behold there was a space character on the end of the string. (I now remember typing that in anew sometime back, but just now got around to testing it). Funny how the Open VI Reference works without error and Exec.State is "BAD" when the path should be no good in the first place. Removed space and it's working.

BillM

Message Edited by Bill@NGC on 07-01-2007 03:31 PM

[mikeporter]

So in other words, adding an extra space after the ".vi" in the file name means the Open VI Reference function finds the VI but when it open it shows up as broken?

This sounds like a bug... Either it should not find the VI and return an error, or find the VI and run it (my vote would be for the later).

Mike...