With record buffering, it's harder to manage since VFP will issue a TableUpdate() internally if the record pointer is moved and you will need an ON ERROR routine to catch it. I would suggest to use 5 - Optimistic table buffering, because it's easier to deal with and you will be sure that the modifications will be commited only when you decide to.

With optimistic table buffering, you just need to check the result of TableUpdate(). If it fail, you can use AError() to get the result of why it failed. Of course, you need to do a TableUpdate() before closing the table, otherwise VFP will try to commit the modifications for you and display an error message if ON ERROR isn't set.

HTH

---

>When buffering mode is set to 3 for optimistic buffering, I think I read that automatic record locking occurs. But do I still have to do commands like REPROCESS and RLOCK and ON ERROR to check for conflicts or does buffering mode 3 take care of all of that for me in a multi-user environment?