I'm seeing this same issue. I was wondering if there was a fix or workaround.

I'm was able to trace this to the cCursor.GetFilePos() method. My view is row buffered. The method sets the cursor's SendUpdates property to .F.

What happens is the GetFilePos() moves the record pointer. Because of row buffering, the view is updated and the field states move from 3's (new record, unchanged) or 4's (new record, changed) to 1's (existing record, unchanged). But, because the SendUpdates property is now .F., the underlying table is not updated, to its values are unchanged (1's).

All of this makes the framework think the current view has data from an existing record on the table. But when we do a SAVE, since the underlying table has not been updated, the framework assumes that another user has changed the data.

There are a few things that I'll look into, if no one has a better solution.
1) Set the field states to 2's (existing, changed). I don't think they can be set back to 3's or 4's from 1's. I'll verify that though. This could cause issue with code that executes on new records (IsAdding())?
2) Set the view to Table Buffering. I would assume it was set to row buffering for a reason. I'll have to check with the designer.

Any help or insights would be appreciated.

Jon Craig
Parity Corp.