Detailed logging to file of errors in dynamic calls

[Mads]

If you do a dynamic call from a built application and it fails because the VI in question depends on a VI that it is unable to locate when called in a built application environment - the only way to figure out what went wrong is to rewrite your app so that it opens the front panel of the VI, and then click on its broken run-button...There should be a way to get that error description without having to do anything with the application.

The real challegne however comes when you run into the same problem on a real-time target. There you can not open the front panel...and basically have to search in the dark to find a solution.

Feedback to the programmer's machine would be nice, but it should not only work when you have LabVIEW running. It should be possible to e.g. put a switch in an INI file...and then get a text log that describes, in full detail, what goes wrong with the dynamic calls.

[AristosQueue (NI)]

Although we might be able to improve the desktop case, we wouldn't be able to do anything about it on a real-time target. There's no compiler on the target, no block diagram to evaluate, not even any description strings so all we can say is "its broken" without being able to say anything about why.

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.