Trouble switching adapter from LabVIEW development to runtime engine

[Gregory]

Hi there,

I have a VI module that runs well using the LabVIEW development adapter, but has trouble when I switch it to the runtime engine. I'm having a hard time characterizing the trouble, but I'm guessing some reference is not held in memory like I think it should be.

My module starts another VI when called through the start asynchronous call node. It then communicates to this VI through a queue, telling it to show its front panel among other things. The front panel never shows, so I wonder if the problem is with the queue reference (in an FGV) or something else... At the end of the module, the asynchronously running VI is stopped, and then it should return to TestStand.

Does anyone have any suggestions? Thank you,

Gregory

[Gregory]

Well I just got some extra info... 

I built the module into an executable and when I try to run it, it says: "The VI is not executable. The full development version of LabVIEW is required to fix the errors."

The run arrow is broken, but it doesn't give me any hint as to what the errors are...

[Gregory]

Well, I've narrowed the problem down to my launcher VI. (If I disable this, I have no trouble running the executable version). I guess this more of a LabVIEW RTE problem than a TestStand question.

[Gregory]

Finally I figured that it is the static VI reference causing trouble. If I disable that, the executable VI is no longer "broken" (though it won't function properly of course). Is there any way around this?