kennethcrooks
New Member
I am currently having a real problem with transactions being extended beyond the scope of the trigger in which they are contained.
An example of the trigger code would be:
DO:
FIND numbers EXCLUSIVE-LOCK WHERE numbers.class = "L" NO-ERROR.
IF AVAILABLE numbers THEN DO:
CREATE logfile.
ASSIGN
logfile.lognumber = numbers.nextnumber
numbers.nextnumber = numbers.nextnumber + 1.
RUN win-other( INPUT logfile.lognumber ). /* This displays a status and does some processing */
END.
END.
Once this trigger block has finished, the lock on the numbers table still exists and does not release the record untill the window containing the trigger code has been closed.
Does anyone know of any reason why this might happen?
An example of the trigger code would be:
DO:
FIND numbers EXCLUSIVE-LOCK WHERE numbers.class = "L" NO-ERROR.
IF AVAILABLE numbers THEN DO:
CREATE logfile.
ASSIGN
logfile.lognumber = numbers.nextnumber
numbers.nextnumber = numbers.nextnumber + 1.
RUN win-other( INPUT logfile.lognumber ). /* This displays a status and does some processing */
END.
END.
Once this trigger block has finished, the lock on the numbers table still exists and does not release the record untill the window containing the trigger code has been closed.
Does anyone know of any reason why this might happen?
