>All of that works fine with local data, as VFP can lock the records in the actual tables. As soon as views are used pess. goes out the window. The view is always buffered optimisitcally as it is local to the workstation and there is no direct link back to the actual table. All data conflicts must be sensed during the write back operation. C/S is all done with views so there is no pessmistic buffering possible.

Thanks for confirming what I was hearing and getting a feeling was going to be happening. I understand why, but it's too bad. I detest op buffering becuase I feel it's a waste of a users time. They fill in all the information and then when they click save, they're told that they can't save it... or whatever I end up doing with the data. Point being, I wish there was some way I could know when they begin to edit instead of them wasting their time.

But, if that's what there is then there's not much I can do about it. I'll have to figure out something as a workaround.

Thanks again.