Hidy John,
I use an add/edit button but timer is good, when I press edit, cannot lock but informed at intervals "still in use ..." or "available..." + the same timer might do a refresh.
Cetin
>Hi Cetin,Edward
>
>In this situation, you almost have to have an "Edit" button to kick off edits rather than free-form text entry, that way you can test RLOCK() before enabling bound controls. At least that's the way I've done it in the past.
>
>
>>>I have a formset in which one of the forms' load method has the following code:
>>>
>>>SET EXCLUS OFF
>>>SET REPROC TO AUTOMATIC
>>>ON ERROR DO ERRORFIX WITH ERROR(),MESSAGE()
>>>
>>>The formset is set to pessimistic buffering.
>>>
>>>When two users try to edit the same record through a data entry screen from the same form, the message "Record is locked - ESC to cancel locking" is displayed. When ESC is pressed, an error message called in errorfix is displayed, then the main application object is released and the program exits. I don't want this to happen. My intent is to clear the lock attempt and keep the form opened.
>>
>>Just my opinion. Do not use "automatic". Have a timer, if rlock() unsuccesfull, display message and enable timer. Timer is there for checking if it can place a lock + displaying still in use while the user is waiting. If s/he navigates to another rec disable timer. Works good with pessimistic.
>>Cetin