In opne of our Mere Mortals based applications, we have an old “ghost user” issue, where we get multi-user conflict errors, even though the system is single user. One cause is as follows:

Copying Records

TableUpdate thinks a change occurred in the base table that now conflicts with the current view/cursor, although, manually, could not find any differences. TableUpdate then triggers an "another user has made changes" error. Later found when copying a record for the problem tables above:
• Data from source record SCATTERed
• Record appended
• GetFldState() initially shows appropriate values for the new record
(3s and/or 4s - appended record)
• Data SCATTERed into the new record.
• Later call to business object’s Refresh method sets GetFldState
values back to 1's and 2's (record not changed or record edited).
• Attempted TableUpdate generates the error.
I'm guessing this causes TableUpdate to think the base table changed, as it now thinks the copied record was simply an edit of an existing record instead of an addition, but the view's new copied record does not exist in the base table. It thinks another user changed the base table.

Other table maintenance routines do not do this, hence they work. The custom record copying code seems to be the same.

Are there any internal FoxPro situations that would change the field state like that?

Thanks