Using .cfr report files in an application

Question

We are developing an application that sits behind a login. In this application we have several .cfr pages. When we try to access one of the reports the web browser returns a blank page. If we remove the application.cfc file from the root directory the pabe works fine. I am assuming the reason for this is the .cfr extension is not being accepted as an application page. Dose anyone know how to correct this? Our servers are windows based and coldfusion is running under iis.
Thanks
Hal Brown

Answer 1

Nope.  If you look at the Help for the "Run VI" method, you find the following information for "Auto Dispose Ref":
"If TRUE, the target VI detaches the reference from the main VI.  When the target VI finishes executing, LabVIEW automatically disposes of the reference, along with the parallel data space.  If FALSE, the main VI retains control of the target VI."
So by setting "Auto dispose" to T, you pass control of the reference to the subVI itself, and LabVIEW will dispose of the reference when the subVI finishes running.
I will second Jeff and urge you to get rid of the global variable!  I haven't used a global variable in something like 14 years.  I haven't needed to.  Myself, I love a good notifier and would urge you to use a notifier instead of a queue if you're going to be spawning VIs.  Why?  Because the first instance of your spawned VI to receive the "stop" message from the queue will remove that message from the queue, thus preventing the other instances from receiving the message.  So you'll have to send the message repeatedly and hope that everyone eventually receives it.  If you use a notifier, anything that contains a "Wait on Notification" with that notifier reference will receive the message.  I think you want multiple listeners here, right?
Ok, this afternoon I'll try to write some dummy code with a statically called VI in it, compile it into an exe, and see if I can duplicate your problem...
One question, were you just using the static VI reference by itself to call your VI, or were you using it the same way I showed in my earlier post, with "Open VI reference"?  I'm just trying to look for differences between what I've done in the past which has worked, and what you're doing now which isn't working...
Jeff, what say you?