>>>> I don't know how to cascade parent key changes to children when it is more than 1 parent record being changed.
>>>
>>>
>>>That's a good problem. There's nothing to link the Inserted and Deleted tables if you've changed the primary key. Is there a candidate key that can be used to relate the children?
>>>
>>
>>That's where I am. I wanted a generic or at least template solution.
>>I started all this by trying to make the databases as similar as possible. At this point it is merely an exercise. The data behavior is similar enough so my app is happy.
>>
>
>Would it be possible to limit parent primary key changes to one parent at a time?
>
>-Mike

This would require application or middle-tier logic, which is certainly possible. I was trying to make the database self-healing, so to speak. The best I came up with was to have the trigger deny updates of more than 1 at a time when the key field is involved. Enforcing it that allows the trigger to make the correlation between inserted and deleted ...