UNLOCK and UNLOCK ALL attempt to release the table header lock. Is it possible that another workstation or automatic process has the table header locked? I'm not sure how/where you are locking and unlocking records so do you have multilocks turned on? Can you verify that locked records are actually unlocked by the workstation or process that locks them?


>Hi folks,
>
>Every 3 to 4 weeks I experience a deadlock that would require starting bunch of servers becuase no user can save records. Basically there are automated processes that run 24/7 and users compete to lock records to update through an App but the automated processes issue explicit 'Rlock' and 'unlock' commands while the App that users are using have only the 'unlock all' command that seems to produce ' can not lock record' scrolling wait window. The frequency of such occurance doesn't suggest a coding issue that is easy to spot.
>
>When I traced through the code in the users App while the deadlock was in place, I found to my surprise that it's triggered by a line that has 'unlock all'.
>
>Did anyone experience such a problem? I would be interested in getting some ideas on what could be taking place here.
>
>Thanks in advance.