3

I have an ArcGIS geodatabase that contains one origin feature class linked to multiple standalone tables by Simple one-to-many Relationship Classes. The foreign keys in the destination tables are all nullable, deliberately, in order to allow shapes in the origin feature class to be edited, merged and (in some cases) deleted. My editing scenario is generally deleting an existing shape and then creating a new one with the same primary key.

ArcGIS behavior sets the foreign key value to "Null" if I delete an origin feature. Even if I delete one shape and create a new one with the same origin key I have to go back into the many linked tables and re-add the foreign key which got set to Null when I deleted the first shape. I need to be able to delete, split, or otherwise edit the origin features without the foreign key being set to "Null."

Can anyone suggest the best workaround to deal with this problem? I'm using a file geodatabase on ArcGIS 10.1 and 10.2 (same behavior in each version). One functionality I need to keep is that when I ID the item on an origin feature class, I need to be able to view (and Edit) all the linked tables.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.