Ok, this might be a lil bigger.
Ok, this might be a lil bigger.
You should not have separate tables for each type of program. Have all programs as records in a table and then link them to the participant as I have shown previously.
The tblPhases also has a problem in that it lists Phase I, Phase II etc. Having sequentially numbered fields is an example of repeating groups which is not a normalized structure. I'm not sure what these phases represent or to what they are associated with but, a structure along these lines would work:
tblPhases
-pkPhaseID primary key, autonumber
-txtPhaseNumber
tblPhaseActivity
-pkPhaseActID primary key, autonumber
-fkParticipantID ????
-fkPhaseID foreign key to tblPhases
-dteStart
-dteEnd
Also you would not have have a separate table of discharged participants. One table to hold all participants and then a related table to tell their status as to current or discharged.
Ahh yes, i was going off what ive been using for the discharged people. There are only 2 phases, and they just have start and end dates. Do i still put them as you set up? And the programs start and end at different times, do i still set up a table for each different group?
Since you have more than one phase it constitutes a one-to-many relationship.
Ok, did a bit of work.
I'm still not clear on what process you are modelling with the database. That helps to understand the relationships.
Regarding your attachment, many of the relationships are missing. Would it be possible to attach the database itself (with any sensitive data removed, of course)?