Solved! Go to Solution.
BugID: NIM097672
Synopsis: Synchronizing edits made by SEARCH CURSOR on existing features in a replica FILE GEODATABASE database with Arc Objects code are failing. After synchronization, only new features are posted on parent database, but no edits to EXISTING FEATURES are posted.
Workaround:
Synchronize the changes from ArcCatalog.
If the features are edited by update cursor then the edits are posted on the parent database.
Is there a setting (rule) that would tell the software to possibly keep the old database information instead of the new database information when editing data, as opposed to the scenario of adding a new record where there is no comparison between records needed which you say is working correctly?
At this least I would log an incident with ESRI to see if they can duplicate this behavior in their environment, in which case if would be a bug that they would need to fix with a future service pack.
BugID: NIM097672
Synopsis: Synchronizing edits made by SEARCH CURSOR on existing features in a replica FILE GEODATABASE database with Arc Objects code are failing. After synchronization, only new features are posted on parent database, but no edits to EXISTING FEATURES are posted.
Workaround:
Synchronize the changes from ArcCatalog.
If the features are edited by update cursor then the edits are posted on the parent database.