>Thank you Gerry - being an amature - its going to take a bit to assimilate you suggestion. I do sincerely appreciate your thoughfulness. Would love to hear more on this from you. Thanks again:)

Keep in touch ... design is an iterative process. What I presented was only a (very) rough sketch.

The suggested tables, indexes and index fields still need to be thought thru. For example, the start and stop times may not be actually required; slot #'s may be sufficient (from a technical POV); only the User may need to see "times".

Model the tables and their relations on paper and determine what "identifies" a cell (ie. week, slot, day/column) and how it can be related to the "appointment pair" (ie. patient + professional + week + day/column + start/stop slot).

The main thing to remember is that "grid cells" are quite flexible when it comes to "presenting" data; they can be tied to a "table.field" or a FUNCTION that accepts parameters and returns a value.

In particular, check out how textboxes (ie. "controls"), etc. are added to Grid columns, and the relationship between "Controls" and ".ControlSource".

Prototyping first with a single grid that shows a "table field" in one column and a "function" in another column wouldn't hurt. From there, one can try adding more columns, putting "containers" within columns, relating 2 grids, and so on.