ArcGIS Server Banner

Creating a composite relationship class (ArcInfo and ArcEditor only)

Creating a composite relationship class (ArcInfo and ArcEditor only)

Release 9.3 E-mail This TopicPrintable VersionGive Us feedback

About creating composite relationship classes

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 composite relationship 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 origin 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.

How to create a composite relationship class (ArcInfo and ArcEditor only)

  1. In the ArcCatalog tree, right-click the geodatabase or feature dataset in which you want to create the new relationship class.
  2. Point to New.
  3. Click Relationship Class.
  4. Type the name for the new relationship class.
  5. Click the Origin table or feature class.
  6. Click the Destination table or feature class.
  7. Click Next.
  8. Click Composite relationship.
  9. Click Next.
  10. Type the forward and backward path labels.
  11. Click the message notification direction.
  12. Click Next.
  13. Click the second cardinality option. A composite relationship is, by definition, a one-to-many or one-to-one relationship.
  14. Click Next.
  15. Click No.
  16. The relationship class does not require attributes in this example.

    If the relationship class requires attributes, click Yes and skip to Creating an attributed relationship class.

  17. Click Next.
  18. Click the drop-down arrow to see a list of fields from the Origin table or feature class. Click the primary key for this feature class or table.
  19. Click the drop-down arrow to see a list of fields in the Destination table or feature class. Only those fields that are the same type as selected in step 17 are displayed. Click the foreign key that refers to the primary key selected in step 17.
  20. Click Next.
  21. Review the options you specified for your new relationship class. If you want to change something, you can go back through the wizard by clicking Back.
  22. When satisfied with your options, click Finish to create the new relationship class.

Tip

  • When creating a one-to-many relationship, whether simple or composite, the one side must be the origin class. The many side must always be the destination class.

See Also

  • Creating a simple relationship class
  • Creating an attributed relationship class
  • Creating relationship rules
  • Relationship class properties