topic Should I create a relationship class, join tables, or relate tables? in Data Management Questions

Should I create a relationship class, join tables, or relate tables?

MatthewLenox — Tue, 10 May 2011 21:38:43 GMT

Hi,

I am working with multiple feature classes that contain the same data. I have a master feature class and I have created multiple feature class "subsets" of that data that I am actively working with. When I edit the master feature class I have to go back and edit all the other "subset" feature classes.

When I edit the master feature class I would like the "subset" feature classes to be updated simultaneously.

Is this possible?

I have tried joining, relating, and creating a relationship class to get the results I am looking for, but have not had luck. I may not be using these functions properly to achieve these results.

Does anyone have any suggestions?

THANKS!!

Re: Should I create a relationship class, join tables, or relate tables?

JakeSkinner — Wed, 11 May 2011 10:18:40 GMT

Is your master feature class stored in an ArcSDE geodatabase? If it is I would recommend replication. You can replicate subsets of the feature class to other SDE, Personal, or File Geodatabases. Then after making changes to the master feature class you can synchronize changes to the child geodatabases.

Re: Should I create a relationship class, join tables, or relate tables?

MatthewLenox — Wed, 11 May 2011 15:26:26 GMT

No they are not stored in an ArcSDE geodatabase. The FC's are stored in personal geodatabases. But if they were from what you suggested, that would be the solution I am looking for!

It's possible the data will be in a ArcSDE geodatabase in the future and if that's the case I will look into replication.

THANKS!!