Record locking examples
- Last Updated: March 30, 2020
- 2 minute read
- OpenEdge
- Version 12.2
- Documentation
Record locking examples
A few simple examples can help illustrate how ABL handles different kinds of locks. When you start the Procedure Editor and connect to the Sports2000 database, you are running in single-user mode, as the only user of the database.
To set up your session to test locking:
- Exit your session to free up your single-user connection to the Sports2000 database.
- Make sure your path includes the bin directory under your OpenEdge install directory.
- From a Windows Command Prompt window, change your directory to your working directory, or wherever your local Sports2000 database is located.
- Type the command: proserve Sports2000. You should see a series of messages as the server starts up.
- Restart the Procedure Editor.
- From the Tools menu, select Database Connections.
- Click the Connect button.
- Type Sports2000 as the Physical
Name, then click the Options button:

- Check on the Multiple Users toggle box
so that you connect to the server in multi-user mode:

- Click OK, then close the Database Connections dialog
box:

Now your session is connected to the database server. To test the effects of record locking in a multi-user environment, you need to create a second OpenEdge session.
To start up another session:
- Start the Procedure Editor.
- From the Tools menu, select Data Administration:

- From the Data Administration menu, select Database, then click Connect.
- Go through the same sequence of steps as before to connect in multi-user mode to the same Sports2000 database server.
Now you're ready to test locking conflicts.