Oh, I see...of course, the child often has two generated key fields, one that can be non-unique (the Child.Parent FK) and then it's own unique PK (if needed) for establishing more relations down the tree structure...

Thanks for the clarification, both of you.

-Irv.

>>Just curious...how would you handle this if the PK was used in a Parent-child relationship with another table? You couldn't just regenerate the PKs without re-establishing the previous relationships, right?
>>
>>-Irv.
>
>As Craig said, the child record PK is the one you change. The relation from the child to the parent is in the Child.ParentFK field (a foreign key pointing to the parent's primary key). Does it make sense?