IMO you can only use optimistic buffering if your system is designed such that you can be optimistic about there being very little to no chance of conflict.

If you have a single record with patient information, drugs and billing information, you will likely have conflicts and would be better off being pesimistic. If on the other hand you had three tables and each table was only updated via an add, the chances of having two people editing the same record are virtually nill and you can afford to be optimistic.

>We have run into a situation with a VFP8 database on a small peer to peer network. When a user tries to save a record, a message "Waiting on Lock" appears and it takes a long time before they can start entering the next record.
>
>We have Table buffering set to pessimistic row buffering. Would it help to change to optimistic row buffering?
>
>Any other suggestions on speeding up data entry would be appreciated.
>
>Thanks in advance.