This content has been marked as final. Show 5 replies
Does the both user trying to update the same record, in that u cannot not.1 person found this helpful
The other user should wait till the first user complete the transaction. This is safe..
What if a user forgets to save , exits the form. And then logs in again in a new session , 'unable to reserve record' message will pop up . Can this be prevented please ? Thanks.
In that case some one will have to interfere and kill the session of the user locking the row.
One more thing. If there was a way to prevent this that would lead to inconsistent database data. On the other hand you can set timeout limits or user inactivity timeout on client/middleware to logoff users not saving changes for a long time.
Edited by: gregor13 on Apr 14, 2013 4:33 PM
When a user exits forms, all his locks will be released so that you don't have that problem. As long as the is the forms and locks the record, the only chance is to kill his session.
i do recommend u using a key-exit trigger or when window close trigger
EXIT_FORM ;Form level or similar trigger to remind user to save the changes made before closing the form & u can follow my guide lines in the following thread to follow up this error
Error - could not reserve record