We had a similar problem - but in a Fox for dos app. Users were able to pick up the same Primary Key value at the same time, even though record locking was enabled, it's quite possible this has happened.

If the 1st user enters an order and saves, and another user has the same PK for another order, then when the info from memory writes back to the table, it will presumably update the already existing order using that PK.

Bit of a long-shot I know, but possible.....

Kev

>Hi folks, from cold but sunny Greensboro (send some rain our way!!)!
>
>One of our programmers is having a little (?) problem.
>
>Here is what the programmer wrote to me...
>
>"Yesterday we had another 'Update Conflict' in the ***** Application, which we have regularly with no problem. However, this time it appears that one operator overwrote an order entered by another. According to Microsoft, this can't happen when you're using buffering, but it does. We had a huge problem with ####### relative to this (a VFP 3) and discovered it was the network driver. Our network admin fixed that and the problem stopped. Now we're having it with our 6.0 apps. After reindexing, I ran all the tables through recovers and it had a delete flag error in ****.dbf. I've seen a relationship between this error and locking problems."
>
>So, have you ever had a problem like this? (2 users entering data (phone calls) at the same time for different clients, yet one overwrites an order for the other). Any ideas before I start pulling what little hair out and dig into the code for the app??
>
>Thanks bunches!!