>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

I'll take a close look at the NextID function that is in the Stored Procedures for this database and see if there is something there causing this.

Thanks!