Object locks were used widely in 6.75 but are only used in a few cases in release 7.0 and beyond. Locks are used to restrict database changes to one user at a time. Locking only applies to Forms and Menus. If a user obtained a lock on an object and did not close the program correctly (due to a power outage, network problem, etc.), then the lock should clear on its own at the end of the expiration period defined in the Object Locking Dialog. Failing that, the administrator can clear object locks here.
Fields |
||
Release |
Use this column to select which locks will be cleared. |
|
Lock ID |
Each lock is given a unique Lock ID when it is obtained. |
|
User Login |
This column identifies the Lucity user name for the user that obtained the lock. |
|
Entity ID |
This column identifies the type of object locked by the user (i.e. Work Order, Submit Process, etc.). |
|
Record ID |
When each record is created, the system gives it a unique Record ID. |
|
Lock Date |
This column indicates the date and time the lock was initially obtained. |
|
Expiration |
This column indicates the date and time the lock is scheduled to expire. |
|
Machine |
This column identifies the name of the computer where the lock was obtained. |
|
Intention |
This column describes the reason the lock was generated. If a record is being deleted, a Delete lock is obtained. If a record is being edited, an Update lock is obtained. |
|
Buttons |
||
Refresh |
Refreshes the data in the manager. This must be done to see any changes. |
|
Release Locks |
Releases any currently selected locks Note: Locks that are shaded in gray cannot be cleared from this grid. Locks are grayed-out for the following reasons:
|