>>..... In any case the "child table" appointments would still have the date.
>
>Why?
The information, about the date of the appointment is required.
Oh, well, an alternative is to have a foreign key to the date table. But in this case I find it simpler to just put the date (or a datetime). If anything special is stored in the date table, I wouldn't consider it as a "parent" table, but as a "lookup" table.
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)
