>In a stateless environment, we use something similar. But, we add another field. Additionaly to one field which is identifying who is having priority to update a record, we also add another field which is an expiration. So, within that timeframe, if the update has not been done, someone else can take over the record. So, on the Web, we usually offer 10 minutes for the save to be done. Depending on the need, this can be greater. After that, if no save is done, someone else can take over it. If no one takes over it, if the main person saves at 12 minutes, it'll work.

Hi Michel.
A similar idea came to me before reading your message. Only i would use only one datetime column which would register the time the user1 began editing. If another user - user2 sees that more that 10 mins passed between the datetime and the now then it means that user1 did not complete editing. The user interface is equipped with the 10 min expiration timer.
Your method adds a conveniance of knowing who was the last user with intention to edit/add a record.
Best wishes.
Kamil