>>>>Bill,
>>>>
>>>>Must be misunderstanding. I didn't say that CLASS_PK is the primary key in the PARTS table. It is the primary key in the PART_CLASS table (new table). (the PARTS table does have the primary key which is not relevant to this).
>>>>
>>>
>>>OK.
>>>
>>>How did you go about setting the foreign key restraint?
>>>
>>>
>>
>>In SSMS I go to PARTS table, right mouse click on Keys and click on New Foreign Key. Then specify that Primary table is PART_CLASS with column CLASS_PK and Foreign table is PARTS with column CLASS_PK. In the UPDATE specification I set to Default on Delete.
>>And then it fails on saving the table.
>
>If that field has 0 in all rows, go ahead and add one row with 0 in the PART_CLASS table. Then you would be able to save your changes in the Parts table.
I was thinking the same. Another approach, I am thinking, is to do away with the constraint at all and add Delete trigger to the PART_CLASS table that would take care of setting the child table value. I am not sure which one is a generally better practice.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
