MIND FREEZE, HELP

[Blanic]

Im really bad at making many to many relationships, I quickly get confused, could someone please sort this problem for me. This is for a doctors appt book.
I have a table for dates, I have a table for appt times (do I need both? maybe combining?), I have a table for patient.
A patient can have many dates and appointments, Dates can have many patients and appointments, times can have many dates and patients? Is this correct thinking? If so, Im not sure how to make the many to many tables correctly.
THANKS TONS
ANdy

 

[chrismcbride]

Unless a date means something other than I think, I think you may have not need the Date table.

One Patient can have one or many Appointments.

One Appointment can have one and only one Patient.

The Appointment record has a Patient (#) and a Date and Time. This would mean no Many-to-Many rlationship, which simlifies things. Additionally it would usually be up to the booking employee to ensure that there is no overlap in the booking, but you could build some logic to support this function.

HTH
Chris