Export out related features

JosephAccardi

I did a forum search for my question and I couldn't find an answer to exactly what I'm looking for. I have a one-to-many relate between a geodatabase feature class and table. I need to find a way to export out a tabular list of all the related features. I can see the related features in ArcMap by using the "Related Tables" tool in the attribute table (http://resources.arcgis.com/en/help/main/10.1/index.html#/Accessing_related_records/005s0000002w000000/) but it only shows the fields in the related table and not the fields from the feature class. Is there a way to view both sets of fields in a relate environment (similarly the way a join works) and be able to export it out into an Excel database?

Or I looked into using a 1:M join based on this help section (http://resources.arcgis.com/en/help/main/10.1/index.html#/About_joining_and_relating_tables/005s0000002n000000/) which states:

When using data where a one-to-many or many-to-many relationship exists, you should use a relate or relationship class to establish the relationship between the datasets. However, it is possible to create a join under these circumstances. When you create a join in such a case, there are differences between how tools and other layer-specific settings work depending on the data source. If you are using geodatabase data to create the join, all matching records are returned. If you are using nondatabase data, like shapefiles or dBASE tables, to create the join, only the first matching record is returned.

But right after this is says: Caution: In all cases of 1:M joins, only the first matching record is joined and displayed in the layer's attribute table.

So I'm confused. It first says that if you are using a geodatabase (which I am) ALL matching records are returned. But since I'm dealing with a one to many join only the first matching record is joined and displayed in the layer's attribute table. Is there a way around this?

JosephAccardi

I found the solution: If your feature class and related table are saved in a geodatabase you can perform a 1:M join. A join within a geodatabase will populate all matching records (not just the first matching record). From there you can export out the feature class to append the related attributes. (http://resources.arcgis.com/en/help/main/10.1/index.html#//005s0000002n000000).