I see what you're saying now.

1. Yes, it's de-normalized, but I don't think speed was the reason, if you catch my drift : )

2. I like this idea and will see if I can coerce the DBA to try it...I just need to figure out how to add the third layer here : ) This also needs to have "appointment ids" in table 3, and the select would need to grab everything for a particular "appointment id" and then sort id for output like:

Appointment:
product: action, action, action
product: action
product: action etc. etc.
[download]

3. The biggest trouble I could see with this would be I would need to do many many inserts for appointments with a lot of products involved in order to populate the records properly. Not too big a deal, but more than I had planned. Off to test : )

-- I'm a solipsist, and so is everyone else. (think about it)