I've always avoided using ObjectIDs when defining relationship classes. It is my understanding that some actions on a geodatabase will re-set objectIDs (like import/export). However I do see a lot of people using them.
Am I just being paranoid, or are there cases when it is safe to use ObjectIDs when defining a relationship class?
Answer
ObjectIDs are only maintained by Copy/Paste. No import or export tool maintains them. It's generally not recommended to user ObjectIDs in relationship classes. If all of your data is truly static it should work ok, but there will always be a risk when you import or export the data.
No comments:
Post a Comment