Current Database Locks

View the current record locks for the database the user is logged into.

RADplus Utilities > Database Record Locking > Current Database Locks

Database locks exist to safeguard client data from integrity issues by preventing the data from being changed in multiple places at the same time. Locks are only enabled while a user has a form open for a particular client.

The Current Database Locks window displays the current database record lock information. This information includes:

• Run Date - The data that this data was collected.
• Job Number - The process ID for the system operation task.
• Username - The username for the user who has locked the information.
• Entity ID - The ID number for the client, or user ID for the staff member whose information is locked.
• Lock Description - The description of what information is locked for the entity. This may indicate that the entire form has been locked for this entity (Shared lock), or identify the specific data that has been locked.
• Form - The name of the form that has locked the information.
• Type - The type of lock that is enabled.
  • S = Shared Lock
    Every form that requires a client ID initiates a Shared lock. This will lock access to that client's data for that form, but will allow the client to be accessed via other shared lock forms. Consequently, multiple forms may have a Shared lock enabled for the same client simultaneously.
  • E = Exclusive Lock
    Certain forms (Change MR#, Client Merge, Client Delete, Delete Last Movement, and Delete Service) initiate an Exclusive lock. This will lock access to that client's data from any other form. You will not be able to access a client from a form with an exclusive lock if the client's data is being accessed from any other form at that time (even one with only a shared lock).

Click Update Display to refresh the Current Database Locks window, to reflect any changes made in myAvatar since opening the form.

Click Print to generate the Current Database Locks report for saving or printing.

To force a lock off, use the Release Database Record Lock form.