Hiya Jim ---

>Or optimistic buffering and securing your own locks either physical or semaphore before allowing an edit to begin. At least with opti buffering you can choose exactly how and when you want to secure a lock on a resource, with Pess buffering you are totally at the mercy of VFP.

Hmmm....OK. So what you are saying is test for LOCK().....if, .T., then proceed with edit under Opt. because, otherwise, another user would have the lock. Works. I think what we are talking about here is just a difference in philosophy with the same results :-) .... btw, I remember there were problems mixing locks with buffering and transactions.

I have a framework I like to use where the parent table, where the form represents one row, is pess. row buffered while children are optimistically table buffered.

However, I must admit, in the simpler situations where collision is unlikely, I sometimes just set everything BufferModeOverride=5 and to hell with it. :-D