>Hilmar
>
>Sorry for the delay.
>
>I'll tell you the situation. We create Assessments for Clients, there are many types of assessments, all on individual tables. There will be the facility on these assessments to add a list of people who have received the assessment.
The thing that still worries me is the possibility of ending up with complicated relations. You might greatly simplify relations having all assessments in a single table. OTOH, if you do this, you may end up with some superfluous fields. Depending on the number of superfluous fields, this may be a small price to pay, for simplicity.
Does one specific client receive only one single assessment? Isn't there a possiblity that some time in the future, some client(s) may receive a second assessment? This would greatly screw up yor original concept.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
