Lock State:Set Method

Short Name: Set Lock State

Installed With: Base Package

Sets the level of editing permission for a LabVIEW project library, including the password.

This method is similar to the Protection box on the General Settings page of the Project Library Properties dialog box.

Note The LabVIEW Datalogging and Supervisory Control Module supports this method in the Run-Time Engine.

Parameters

Name	Required	Description
lock state	No	Specifies the level of editing permission to set. Not locked—Users can view public and private items that the project library owns and can edit the project library and its properties. Locked (no password)—Users cannot add or remove items from the project library, edit project library properties, or view private items that the project library owns. Password-protected—Users cannot add or remove items from the project library, edit project library properties, or view private items that the project library owns. Users must enter a password to edit the project library.
interactive	No	Specifies the way in which you can use passwords with the project library. The default is FALSE, in which you can use a password to unlock a password-protected project library or to set the password of an unprotected project library. If you set interactive to TRUE, LabVIEW ignores the password and displays a dialog box that prompts you to change the lock state.
password	No	Specifies the password to set for a project library to which you want to add password protection, or the password to use to unlock a password-protected project library.
put in cache	No	Specifies whether you want to cache the password specified in password. The default is FALSE, which does not add the password to the LabVIEW password cache.

The following table lists the characteristics of this method.

Available in Run-Time Engine and Real-Time Operating System	No
Settable when the VI is running	No
Loads the front panel into memory	No
Need to authenticate before use	No
Loads the block diagram into memory	No
Remote access disallowed	No
Must wait until user interface is idle	No
Available with control VIs	No
Available with global VIs	No
Available with strict type definitions	No
Available with polymorphic VIs	No