Basically optimistic..
Our app works with Foxpro now. And uses Buffering set to 5...

If you mean should I hold the lock or only when updating.
The idea is only when updating..
edit button clicked...
BEGIN TRANSACTION
Call the function to lock...(Via SELECT for update ect..)
Make update statement....and update record..
END (COMMIT) TRANSACTION
save or cancel button clicked...

Would be similar in foxpro to...
edit button clicked...
RLOCK()
REPLACE....
TABLEUPDATE()
UNLOCK()
save or cancel button clicked...

BUT...There is one activity where i must lock the entire system...
However, I could just lock an access rights table.
There are many ways to do it for me.

But I'll take what I can get....
Why do you ask?