Ken,
We did a similar schedule for a golf course - so people could tee off at varying intervals. In this case they varied throughout the day - longer times early and late, shorter midday when the course was crowded. We used a 'day model' table that laid out time increments in minutes and the start/stop times of each section

Start     Stop    Increment
5am      7am    15 min
7am      2pm    10 min
2pm      4pm    15 min

Users could pick a day model for any day (or assign one to all weekdays in January). In OUR case, if the user switched models the appointment (tee time) stayed with the 'increment number' - how many increments from the beginning of the day. In your case it might need to be time linked.

There was a table of models, a detail table which showed the data above and then a calendar table which linked the assigned day model to each day of the year. Sounds elaborate, but it loaded very rapidly, as they 'paged' through their calendar.

One hint: Be SURE you use military time for all storage and calculations, even if you display times as am/pm. You'll hate yourself if you don't!

HTH
Barbara

>I'm trying to design an appointment app. for my office and am struggling with table design. Usually this is the easiest part.
>I want to break the day into variable time increments (ie 10,15,20 minutes slots) and have separate schedules for 3 different people. The data would be display in grid form.
>
>This request may be beyond the scope of this forum, but any ideas would be welcome.