LabVIEW
Stop and Quit LabVIEW Vi in Development Environment
Oh, and it is better practice to make an executable. It's not that much work, and will save you a lot of problems.
An executable will automatically shutdown when all stopped VI's are closed. So instead of calling Quit LabVIEW, you only have to make sure all VI's stopped running and that their FP's are closed. Stopped running you should get automatically (natural end of a running VI), and often the main is the only open FP. You can still use Quit LabVIEW, but use a conditional disabled structure (or Boolean input) to only execute it in run time environment.
Why is an exe better? Well, for one you can develop in LabVIEW, while the VI (exe) is started by the CL. Without the exe, LabVIEW will be closed while your doing something else in LabVIEW.
Also, each time you run the VI for test, it will stop LabVIEW. That gets old fast...
Search LabVIEW like a graph! 
