This object is created when there is a timeout while waiting for a record lock (based on the -lkwtmo startup parameter), or by hitting Cancel on the lock conflict wait dialog. Note that in character mode (Linux, Unix or character mode in Windows), you can hit CTRL+C or CTRL+Break to stop waiting. However, the AVM still maps that to the LockConflict object due to the context, not to the Progress.Lang.UserInterrupt object.This class inherits from Progress.Lang.Stop and thus inherits the CallStack property. It also has three properties of its own. These all correspond to the same information that is shown in the lock conflict wait dialog box.

Table 1. Progress.Lang.LockConflict properties
Member Description
TableName property This is the name of the database table that has the lock conflict.
User property This is the name of the user that is currently holding the lock and thus causing the lock conflict.
Device property This is the name of the device on which the other AVM process is running that is holding the lock and thus causing the lock conflict. Alternatively, this can be “Dictionary” if another process is doing schema updates via the Dictionary. The format of this name is different on different operating systems.