A few simple examples can help illustrate how ABL handles different kinds of locks. When you start the Procedure Editor and connect to the Sports2020 database, you are running in single-user mode, as the only user of the database.

To set up your session to test locking:

1. Exit your session to free up your single-user connection to the Sports2020 database.
2. From a Proenv command prompt, change your directory to your working directory, or wherever your local Sports2020 database is located.
3. Type the command: proserve sports2020. You should see a series of messages as the server starts up.
4. Start the Procedure Editor.
5. From the Tools menu, select Data Administration > Database > Connect.
6. Click the Browse button, select the sports2020.db, and click Open,

   

7. Click the Options>> button, check the Multiple Users checkbox, and click OK so that you connect to the server in multi-user mode:

   

8. Close the Data Dictionary.

   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:

1. Start another Procedure Editor.
2. Go through the same sequence of steps as before to connect in multi-user mode to the same Sports2020 database server.
3. Close the Data Administration window.

Now you are ready to test locking conflicts.