In the ArcGIS Desktop help topic, Modeling limitations of relationship classes, please allow multiple fields to be used to define the primary and/or secondary keys that define the relationship classes, as well as in-memory relates:
The primary and foreign keys can each be based on one field only; complex primary and foreign keys are not supported in ArcGIS.
I was hoping that this would be resolved back when 9.0 came out, and was yet again disappointed seeing it didn't make it into 10.0 even.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.