I am trying to figure out what is the best way to lay out my situation.
I am designing a drug testing database. I need to be able to "sign" a donor in for a test(s) for drugs. It could be 1 drug, or 5 drugs. When the donor is signed in, i need a date and timestamp to be placed on that test for that day. But I also need to have the database allow the user(the company that will use the database)to create their own tests(In case there is a drug that the company needs testing for that I don't already have on the list)
I was told to have 3 tables, one for the Donor(with personal info on it), a table for the drugs(with drugs listed in rows, rather than drugs listed as fields, allowing them to have an autonumber id) and an intersecting table with both of those primary keys). I was told also to use a combo box to select the drugs(but a combo box can only let you select one item right?)
If I did it that way, each donor that had a test would have a lot of drug test ID numbers for each drug being tested. Anyway can someone clarify my problem?
I am designing a drug testing database. I need to be able to "sign" a donor in for a test(s) for drugs. It could be 1 drug, or 5 drugs. When the donor is signed in, i need a date and timestamp to be placed on that test for that day. But I also need to have the database allow the user(the company that will use the database)to create their own tests(In case there is a drug that the company needs testing for that I don't already have on the list)
I was told to have 3 tables, one for the Donor(with personal info on it), a table for the drugs(with drugs listed in rows, rather than drugs listed as fields, allowing them to have an autonumber id) and an intersecting table with both of those primary keys). I was told also to use a combo box to select the drugs(but a combo box can only let you select one item right?)
If I did it that way, each donor that had a test would have a lot of drug test ID numbers for each drug being tested. Anyway can someone clarify my problem?