Hi All,
I have an app that is using optimistic row buffering in a client info table and have run into the following problem.
User 1 goes to record Client 1
User 2 goes to record Client 1
User 1 adds a major evaluation about Client 1 in a memo field . Moves on. TableUpdate is no problem.
User 2 changes one small item or no items. Moves on after User 1. TableUpdate() returns .f. and User 2 decides to overwrite User1. User1's memo field is overwritten with the blank memo field and User1 is now really irked!

In this case I thought I'd switch to pessimistic Row Buffering, trap the lock error if another user started editing the same record and display a form telling the user that the record was being modified by someone else and to try again later. I don't see what the difference is between this and not buffering the table at all and trapping the same lock error.

Any thoughts would be appreciated!
Thanks,
Bill