NOTE: Although relationship classes can be both created and edited in ArcInfo and ArcEditor, they are read-only in ArcView. The feature classes participating in a relationship class will also be read-only in ArcView.
You can use a wizard to create a
class. The example in this subtask shows how to create a relationship class between a feature class that stores transformer banks and one that stores transformer units.
The existence of a transformer unit in the database is dependent on the presence of a transformer bank. This relationship class is a composite relationship with the transformer bank as the
feature class.
The relationship will be nonattributed; composite relationships are by definition one-to-many (1:M) relationships.
Creating a composite relationship involves many of the same steps used in the task for
creating a simple relationship. The steps outlined here reflect the differences between the two tasks, including using different origin and destination classes.
Learn more about creating a simple relationship class.
Learn more about creating an attributed relationship class.