>>>I have an application that currently uses Pess. Row Buffering. The problem is in the following situation : User A and User B access/read a client record at the same time. User A then locks the record while making changes. User A TABLEUPDATES() and commits the changes. In the meantime User B answered his/her phone and currently has the original record on thier screen. They proceed to modify. When they click on an object ( in this case a popup) before it drops down I (User B) sees a status bar message saying the record has been modified by another user. I guess my two questions are: Can I intercept that message somewhere in code and give he user a proper message? or What is the least coding intensive approach to solving the situation ? The record being modifed has 75 fields display on multiple pageframes. I hoping putting code in the click or When methods of each is not the easist solution.
>>>
>>>Any advice would greatly appreciated.
>>>
>>>Thanks
>>>
>>>
>>>
>>>Scott K
>>
>>I think the better ways are to use either optimistic buffering where you easily inercept conflicts while TABLEUPDATE(), or use non-buffered RLOCK() approach, which is actually 'pessimistic' by nature but with full code control.
>
>Thanks Again.
>
>It seems the old logic hasen't died

The idea of buffering is derived from two sources: remote views which require it and simplified form development when you can drag fields from DE to Form Designer (ControlSources are filled automatically and then buffering is required again to handle multi-user conflicts). In case of unbound controls RLOCK() still works pretty good.