Maybe he wants to enforce a key, maybe between a lookup table in one dataset and the transactional data in another? My work usually splits up the datasets this way (sometimes more).
When Ive needed it, Ive included the lookup table in both datasets. Mostly I would handle this through custome code to enforce the constraint, treating it like any other business rule. Normally a user would only get to change the value through a DropDown or some other means - effectively forcing them into a constrained value.
-ner