Table Design



I need to design a database that will track the history of patients on a
study drug. I need to track Adverse Events and a number of other things.
Their medications I would also need to track. What would be the best way to
design the table. There will be a number of adverse events. So would I have a
table specifically for adverse events and another for medications. Or would I
have just one table with columns named Adverse Event 1, Adverse Event 2 etc.
and medicaton 1, medication 2 etc. There will be different numbers of Adverse
Events and Medications depending on the patient.

Thanks very much for any help.

Best regards,


Lynn Trapp

First, let me suggest that you get a copy of Database Design for Mere
Mortals by Michael Hernandez. Second, except in exceedingly rare instances
you don't ever want to name fields like [Adverse Event1], [Adverse Event2],
etc. Those are referred to as repeated fields and you need to pull them into
a separate table.

Lynn Trapp
MS Access MVP
Access Security:
Jeff Conrad's Access Junkie List:

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question