Jesse B

Yeah, that does make sense to just have the program quit entirely whenever the user clicks "STOP", or to just have it always running and then the "RUN" and "STOP" buttons apply to an inner loop in the program. The situation we had was users would sometimes want to investigate signals in Measurement & Automation Explorer, but were unable to do so while the program was running since those I/O channels become reserved by the program. In this case, it sounds like the always running but having a "RUN" and "STOP" button for an inner loop would work best. Thanks again, Jesse.

I am currently building a LabVIEW application for use in our analyzer labs. I can get the application to run upon opening the program, but once the user ends the VI with a large "STOP" button I created, that user cannot get the program to run again without clicking the small white arrow on the upper-left corner of the screen. Some of the users who are unfamiliar with LabVIEW have a difficult time finding the run button. Is there a way to create a large "RUN" button on the front panel that tells the VI to run? Thanks in advance.