Asynchronous VI Run : Get explicit error message when VI is broken ...

[manu.NET]

Hello,

In many of my applications i had to run dynamic assynchronous VIs using a VI path.

When the VI you want to launch has some problems (VI broken, missing ressources, ... ) you get the generic error 1003. (The VI you want to launch may be broken ... ? )

This error can be easily solved when you are using LabVIEW IDE. 

But sometimes, this error can occured in an executable you have deployed to your final user computer.

And then, the error 1003 (The VI you try to call may be broken ... ) is a little bit poor in order to analyse the problem.

This error occurs, for example, when the dynamic VI tryes to access missing DLL's.

It would be nice, if the error 1003 message, could be filled out with and additionnal "error description", giving more informations about the error source.

For example, an error list, like the error list in the LabVIEW IDE. (Broken arrow error list !)

Thanks a lot.

Manu.

[StephenB]

Steen I've delt with all the debugging limitations with built LVRT apps for so long I just use print debug string now. It is so frustrating to me I don't even bother writing up the issues anymore. Thank you very much for taking the time to document the pain full experience. one other thing is even when you do somehow get a trace to work... Its serous voodoo magic to try to 1) find the issue in a huge trace log and then 2) correlate the issue in the trace back to the code. The people on my team at work think I'm a hero because I happen to have a 25% success rate at that, hah. I wish I could search for stuff and then double click somewhere and be taken to the code where that happened. but we have somewhat hijacked the thread now... Sorry