Releasing Database Locks 

During Debugging, the COMMIT statement may occur after a significant number of debugging steps. Any database locks that are set are maintained for the whole of this time ( see also Debugging in Production Clients).

There may be occasions when you want to interrupt your testing without actually ending the debugging session. In this case, you should release the database locks, otherwise other users will not be able to make changes until your debugging session is finished.

To do this, choose Debugging ® Database ® Commit (unlock). Remember that this could, in certain circumstances, lead to database inconsistencies.

If you want to undo all of the database changes that have been made since the last commit, choose Debugging ® Database ® Rollback.