The GDB_ReplicaChanges table is not updated when using Python to alter a record in a personal geodatabase (mdb) outside an edit session.
Last Published: August 19, 2020No Product Found
Bug ID Number
NIM074143
Submitted
October 17, 2011
Last Modified
April 2, 2025
Applies to
No Product Found
Version found
10.0
Status
Will Not Be Addressed
The development team has considered the issue or request and concluded it will not be addressed. The issue's Additional Information section may contain further explanation.
Additional Information
We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.
Workaround
Note: Using the following steps in an edit session changes get to be updated in the GDB_ReplicaChanges table. When the synchronize operation is run the SQL express database is updated successfully.1. Create replica with the Distributed Geodatabase toolbar and choose type check-out to a personal geodatabase (mdb), no further options.2. Add feature class to ArcMap from the checkout database.3. Start editing on the feature class.4. Open Python window and copy the script and run it.5. Stop editing and save edits.6. Launch Microsoft Access and open the mdb > GDB_ReplicaChanges> the deleted record will be listed.7. From ArcMap > Distributed Geodatabase toolbar> Synchronize Changes.8. Check the SQL express geodatabase. The OBJECTID specified in the script for deletion has been deleted.