>Hi Nadya,
>
>It appear the suggested three table model has some duplication, and is not well normalized. It would be better to have a more traditional two table model with a parent child relationship. This would make it easier to enforce referential integrity. Through the use of SQL, you could present info to a prospective buyer in either a summary or detailed report achieving the same result of the more complicated three table model.
>
>LelandJ
You might be right. I also objected 3 tables model and insisted on the easier 2 tables model. However, I thought, that 2 tables model could not be converted into 3...
Anyway, it's hard to convince my manager, because he is using this "Chang" sample in about 15 (or more e-mails) and thinks that's the way to go... I asked again yesterday our business folks to make a decision, but got reply only from Joe. I guess, I have to do it this way.
Bob Archer already gave me a good starting point for the SP...
If it's not broken, fix it until it is.
My Blog