Hi Guys
Can anyone explain why this code would raise the locked by another user error in the form of a message box with an OK button as opposed to the standard message box which informs of the lock then closes automatically when the lock is released (as happens previously in the executed code)? ](*,)
Client 3.70.B DB 2.01.B Native
Life is for enjoying ... if you find yourself frowning you're doing something wrong
0
Comments
2) if not 1) then, are you sure there is no LOCKTABLE(TRUE,...) before current one in the same transaction? (I am not completely sure that the first LOCKTABLE will be kept or if the second will be used)
In these cases it is normal behaviour.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Thanks for the quick reply, I am definitely sure it's LOCKTABLE(TRUE, the puzzling thing is the error message with the OK button and not a message that's shown and disappears?
I don't think this table is locked previously within this transaction however other tables are locked.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!