>In the first case I could have a field date and I child table with unlimited appointments
>The date in in format dd/mm/yy, a table only to be parent of the child table containing
>the hours
>
>In the second there will be a limited number of fields for schedule
>
>Each field will be named as a time: 8am, 830am, 9am, 10am, etc
In this case, I find it much simpler to have the date as a field in the table. The only reason to keep a separate table for dates is, if you need to store specific information that belongs to dates, and not to individual appointments. Like Agnes said, for holidays. You can store additional information about holidays, e.g., what are you celebrating. In any case the "child table" appointments would still have the date.
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)
