Humm, good point.


>What about if the client crashes, the network goes down or any unpredictable situation arise, then what append to your lock?
>
>>When the application locks the record there will be timer control will worn the user to finish the edit if he took long time, the timer has the ability to cancel the record lock according to some rules.
>>
>>
>>>This is called pessimistic record locking. Be prepared for lots of contention. What if someone click modify and then walks away for lunch or goes home?
>>>
>>>>When 1st user open the record, data will be displayed as view only in the form, then if he desided to update some data he should click "Modify" button, when he clicks it, the system will lock the record till he saves the data.
>>>>
>>>>Now, when another user try to modify the same record, a worning message will appear saying this record is being updated and will stay in view mode till the first user relase the record.
>>>>
>>>>Record lock will stop user conflicts.