Jodi,
Rather than define a code set, that you would have to constantly update as changes are made to the source repository, I recommend you leverage the custom control capability in the profile containing the attribute to have the selection list based off the values of the source repository. You can define a custom control on the attribute of interest of type "Custom Search Control Dynamic" and define the SQL necessary to retrieve the list of unique values from the source repository. As records are changed in this repository, the drop-down for the attribute will reflect those changes. Such a control should be accompanied by a Bulk Callout validation rule that has a variant of the same SQL query to flag any value in the attribute of interest if it is not one of the values found in the source repository. The Brown Bag Session #26 covers custom controls in detail. The support web site has a KB article on defining bulk callout validation rules.
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 9099009179
------------------------------