Note: This topic was updated for 9.3.1.
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.
Any relationship class—whether simple or composite, of any particular cardinality—can have attributes. Relationship classes with attributes are stored in a table in the database. This table contains at least the foreign key to the origin feature class or table and the foreign key to the destination feature class or table.
An attributed relationship can also contain any other attribute. The example in this subtask shows how to create a simple relationship between a feature class that stores water laterals and a feature class that stores hydrants.
Water lateral objects have their own attributes, and hydrant objects have their own attributes. The relationship class in this example describes which water laterals feed which hydrants. Because you want to store some kind of information about that relationship—such as the type of riser connecting the two—you can store this information as attributes in the relationship class.
Learn more about creating a simple relationship class.
Learn more about creating a composite relationship class.