关于ARCGIS9.2的问题！！

<P>大家来看一下，本人用的是ARCGIS9.2</P>
<P>我的catalog里面个人数据库NEW菜单为什么没有关系数据类——relationship class?<BR>那位高手明白？是不是设置问题还是软件问题？ 谢谢！！</P>

How to create a composite relationship class (ArcInfo and ArcEditor only)
<DIV>
<OL>
<LI>In the ArcCatalog tree, right-click the geodatabase or feature dataset in which you want to create the new relationship class.
<P></P>
<LI>Point to New.
<P></P>
<LI>Click Relationship Class.
<P></P>
<LI>Type the name for the new relationship class.
<P></P>
<LI>Click the Origin table or feature class.
<P></P>
<LI>Click the Destination table or feature class.
<P></P>
<LI>Click Next.
<P></P>
<LI>Click Composite relationship.
<P></P>
<LI>Click Next.
<P></P>
<LI>Type the forward and backward path labels.
<P></P>
<LI>Click the message notification direction.
<P></P>
<LI>Click Next.
<P></P>
<LI>Click the second cardinality option. A composite relationship is, by definition, a one-to-many or one-to-one relationship.
<P></P>
<LI>Click Next.
<P></P>
<LI>Click No.
<P></P>The relationship class does not require attributes in this example.
<P></P>If the relationship class requires attributes, click Yes and skip to <a href="ms-its:D:\program target="_blank" >Creating an attributed relationship class</A>.
<P></P>
<br>
<LI>Click Next.
<P></P>
<LI>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.
<P></P>
<LI>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.
<P></P>
<LI>Click Next.
<P></P>
<LI>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.
<P></P>
<LI>When satisfied with your options, click Finish to create the new relationship class. </LI></OL>
<P></P>
<TABLE cellPadding=5 width="85%" border=0>

<TR>
<TD>
<H3>Tip</H3>
<UL>
<LI>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. </LI></UL></TD></TR></TABLE></DIV>