Being quite an old thread, the importance has nevertheless not changed, nor has the state of solutions. I found something rather weird, but ingenious at the same time. Check it out:
comrade's "Find truly executing VIs by trying to save the run-time menu" is nice if the code will only run in LabVIEW (especially since you can output to a nul device "\\.\NUL" to avoid actual disk access) but that property is not available at run-time.
> I think this could also be a solution for your problem.
Sushant_Kumar, the problem with your solution is that it will output Running even when it is just Waiting to Run (i.e., when its caller is running but it is not).
