>>>(The point of my discussing this with you, Borislav, is not to argue, but rather so that I finally have all these terms firmly understood in my head).
>>
>>In the scenario you described the parent's identity field is unnecessary since your PK is CustomerID - (taken from the user).
>
>This is exactly what I was saying. I want Borislav to dispute me <g>.
Why would he in this case when it's obvious? He probably suggested to use identity PK as a primary key (and a foreign key for child tables). Since this is not a case for you and I guess you ensure uniqueness somehow from the front-end (database will ensure it as well), then it's OK.
If it's not broken, fix it until it is.
My Blog