If your team works on a shared database, you can lock objects so other people can't edit the objects while you're working on them. This means teams don't accidentally overwrite work.
After you lock an object, you can work on it and check it in as usual. When you try to edit an object locked by someone else, the server returns an error. You can still unlock other people's objects if you need to.
To use object locking, a SQL script needs to be run on the database. You can do this from the Lock objects tab, or you can run the script manually. For more information, and to view the script, see Setting up object locking.
Using the Lock objects tab
After locking is set up, the top pane lists objects that are currently locked in the database. The bottom pane lists objects that are currently unlocked.
The tab shows:
- the name of the object
- the type of object
- who the object was locked by
- the date the object was locked
- when the object was last edited
- the comment left by the person locking it (if one was provided)
To lock an object:
- In the Unlocked objects pane, select the object you want to lock.
Type a comment explaining why you're locking the object (optional).
Click Lock selected objects.
The object is locked and appears in the Locked objects pane. The rest of your team can see you've locked the object and won't be able to edit it until it's unlocked.
To unlock objects, select the objects in the Locked objects pane and click Unlock selected objects.
To unlock objects you locked yourself, click Unlock all my objects.
For an example of how a team might use object locking, see Example - locking objects.