Modeling limitations of relationship classes (ArcInfo and ArcEditor only)
Modeling limitations of relationship classes (ArcInfo and ArcEditor only)
Release 9.3
Note: This topic was updated for 9.3.1.
A feature class or table can participate in more than one relationship class. The only restrictions are
A given feature class or table cannot be the destination in two composite relationship classes.
If a composite relationship class exists between two classes, no other relationship class can be created between the same two classes.
You must avoid setting up a relationship class between feature classes in a geometric network, because this can lead to unexpected results when you edit the data.
You can have more than one simple relationship between a pair of classes. You may do this if you need to enforce different cardinality depending on the direction you navigate the relationship.
Recursive relationships in which a relationship exists between records in the same feature class or table are not yet supported in ArcGIS.
The primary and foreign keys can each be based on one field only; complex primary and foreign keys are not supported in ArcGIS.
To create a relationship class in a feature dataset, either the origin or destination class must be in the feature dataset.
There are no limitations with respect to differing resolution. Simple and composite relationship classes can be made up of feature classes of different resolutions.
