>Thank you for all suggestions
>
>
>I was considering two options
>
>
>1- Create a table for dates and a child table for appointments
>(in this case appointments are records)
>
>2- Create a unique table where date and appointments are fields
>
>As the second option seems easy to me, I would like to know
>if there are chances of having problems if I choose it
>
>
>Moises

We store the appointment date with the appointment (1 table). Then we have another table that holds Holidays/non-work days/work hours. It also holds exceptions to the rules as well. If you normally work 8-5 on Monday but on July 3rd you only work 8-12:00 that same table holds that value as well. The key for us is if there is a date in the key field then that work hours are for that date if we can't find it then we search for CDOW() of the date we are looking at and that's the default working hours.

We don't keep a list of all days we just add the appointments to the day it says and show holidays/non-work days as a different color. If the date isn't in the holiday/non-work day table we figure it's a work day.