Patient Database
Tuesday July 29, 2008
In a recent forum posting, mbuffet wrote:
"I have a PatientID field in 2 different tables (General Information and Diagnosis) so that I can make a relationship between the two. Do I have to input the PatientID data for each table individually or is there a way to enter the information once in a form and populate both tables?
Is it a bad idea to declare the PatientID field as the primary key for each table? I was thinking of using this identifier for all the tables."
Do you have any advice? Interested in answers to this question? Join our forum discussion.
"I have a PatientID field in 2 different tables (General Information and Diagnosis) so that I can make a relationship between the two. Do I have to input the PatientID data for each table individually or is there a way to enter the information once in a form and populate both tables?
Is it a bad idea to declare the PatientID field as the primary key for each table? I was thinking of using this identifier for all the tables."
Do you have any advice? Interested in answers to this question? Join our forum discussion.
Using MS Access – One Patient may have many diagnoses at different times – so the PatientID should not be the key field on the Diagnosis Table – it is a foreign key in the Diagnosis Table with a one (Patient details)to many (Diagnosis) relationship.
If you have a main form with the General Details with a subform for the diagnoses then the PatientID can automatically be filled in the Diagnosis table.