I'm not saying not to use SSN...just that if you get matches, they may be different people.

>Hi, Craig,
>
>Yes, but this is an issue where we've already put the numbers into the second table, and we are attempting to do a JOIN on the SSN's for other purposes, and to search for existing instances of the same person's record to avoid duplicate entries.
>
>I know we shouldn't use them as a general rule, but we are working with two completely separate data tables from different agencies, both of which have their own primary key. The SSN, imperfect as it is, potentially is the the best common field to match on.