Ok, this one is driving me batty. My client says that sometimes when they create a new record in my application, the 'new' record isn't at all blank, in fact it contains data from a different record. But this in NO WAY causes a problem with that other record - and if they replace field values and save the new record, it's just fine. Both the old record that was showing up and the newly entered record are intact, no corruption. Of course, this does not happen every single time. Nor have they had it happen when I was on site and could see it. I've tried running multiple instances of the app on my home network to see if it's some odd multi-user issue, but also cannot duplicate the problem.
This problem appears when creating a new child record, which has it's own form. The code does an append blank and then replaces the blank foreign key value with the proper value before activating the user interface. The app uses a standard VFP DBC, optimistic buffering. All I cna come up with is that maybe two users hit the add simultaneously, or one user has created a new record but hasn't executed the save yet, and when user #2 does an add the record pointer is in the wrong place. But I think something like that would cause data corruption, or at the very least a primary key conflict, neither of which occur.
Any suggestions on what I should look at?

TIA,
Randy