AFAIK the general approach is to use tablebuffering and let VFP to handle conflicts (you need form's Error routine to provide some info back to the user).

Since you're using different approach using temp cursors, you need to show us some code how exactly you're handling multi-user issue yourself.

>I'm hoping somebody can shine some light on an issue that I have.
>
>I have a contact management system that is used by several employees. Generally anywhere from 1 to 6 people. Every now and again a user claims that information they had entered had dissappeared. Now, after said employees have been alerted and are keeping very good watch for anything out of the ordinary I have found that these issues only occur when two people save their changes at the same time. In fact.... it often flips the records about:
>
>Employee A saves the contact: "Sam Junior"
>Employee B saves the contact: "George Foreman"
>
>Result: two records of "George Foreman" and no Sam Junior to be found...
>
>I had been using buffering on the table earlier but it was necessary to move away from that and all contact data is now held in a cursor. The master table is updated when the user clicks the save button. No tableupdate() is issued. The master contact table resides on a network drive accessible by all employees.
>
>Please, any insights, comments, suggestions on this issue would be greatly appreciated. I have been developing in VFP now for 4 years and have never seen anything like this before.