Validating Features - Relationship Classes and Orphans in Destination Table

WesKing — Wed, 03 Jul 2013 21:37:28 GMT

Hi Everyone:
Using 10.1 file geodatabase, I have a feature class in a dataset and a table in the geodatabase. Feature class is the origin and table is the destination. No matter what I try I can't seem to enforce that a record in the destination table must have a matching record in the origin feature class. Example...I can open the destination table and add a record, which has no related record in the origin table. Since the table records are not features I can't run Validate Features directly on this table. I have tried simple and composite relationship classes, setting a rule for specific cardinality, and creating 2 relationship classes (1 going from A to B and 1 going from B to A).

I have read many help pages and it seems so simple, but I am missing something. If you have any advice I'd greatly appreciate it.

Thanks in advance,
Wes

Re: Validating Features - Relationship Classes and Orphans in Destination Table

ToddHenry1 — Sun, 05 Jul 2015 15:36:03 GMT

I have the same question. Did you get an answer to this question?

topic Validating Features - Relationship Classes and Orphans in Destination Table in Data Management Questions

Validating Features - Relationship Classes and Orphans in Destination Table

Re: Validating Features - Relationship Classes and Orphans in Destination Table