How to prevent user from making changes via the menu bar for Labiew built app.

[mStevenson7]

When an application terminates in LabVIEW the menu bar becomes visable (even if it was removed when running).  How can an operator be prevented from making changes using the menu bar?  For example, the check box for "Run with multipule threads" under Tools>Options doesn't look like something we would want the user to be able to change.  How can the operator be disallowed from making this kind of change?

[Dennis_Knutson]

A built application should have a Quit LabVIEW function in it and the front panel will completely close and disappear so there is no way for a user to access the menu.

So that you can have the function in your development system and not exit has been discussed numerous times. One typical way is to use the App.Kind property and only exit if the kind is 'Run Time system'.

[mStevenson7]

That might solve it.  However, it looks like the <app_name>.ini file is where changes are saved.  Is there a way to make the application only load default ini values when started up?

[Dennis_Knutson]

You're afraid an operator will make changes to the ini file? Frankly, I've never worried about that since it would require a very sophisticated operator to know what would be valid and what wouldn't. It would probably take a fairly sophisticated LabVIEW programmer for that matter. I don't know of any way to prevent a modified ini file from being loaded.

[RobCole]

I just ran a test where the program I built deletes its own .INI file when it exits. This works. Changing the configuration (my VI does not exit LabVIEW) does not get saved after the VI has already ended. My VI runs the way I expected it to every run. It must be using some default settings. I didn't see anything in the .INI that was required. this may change if you need the webserver or VI server enabled.

     Rob