Hello,
Ok ok... only 4 stars for that effort... let's see if we can do better 🙂
First, I see the same behavior upon closing the application I originally attached - the chm also closes 😞
Apparently what's happening is that when we use the online help control VI, the chm file is opening in the calling application's context, in this case the LabVIEW app/runtime engine instance.
We can get around this by making a call which will open the chm file explicity in Windows - we can do this from LabVIEW with the command exec VI.
I have attached the code this time as well - everything is zipped up (lvproj, vi, & exe). You'll notice I have used a diagram disable structure so you can see both implementations - the previous one is disabled of course.
I hope THIS is what you were looking for 🙂
Best Regards,
JLS
PS - if you want your LabVIEW application to close by itself after it completes execution, you can use the Exit LabVIEW function at the end of the VI and rebuild the exe.
Message Edited by JLS on 04-20-2007 12:25 PM