Seems like you need a third table, Participation, so you can have one table that lists each person, one table that lists each training activity and a third table that links a Person record to an Activity record to log that person's participation in a given activity.
If so, this is a typical many to many relationship and you can set it up like this:
Personnel::PersonnelID = Participation::PersonnelID
TrainingActivities::ActivityID = Participation::ActivityID
WIth this set up a portal to participation on the Personnel layout will list all training activities in which that person participated. A portal to Participation on the TrainingActivities layout, on the other hand, will list all personnel that participated.
You may find this demo file on many to many relationships helpful: http://www.4shared.com/file/dZ0bjclw/ManyToManywDemoWExtras.html
Makes sense, but it's still not working. Thanks for the demo file Phil, however differences from that example to what I am doing make it difficult for me to make the translation.
I created the 3rd table for the many to many relationship. Then pointed the portal to that 3rd table. But the portal just shows blank fields, no data (i.e, no list of training activities).
In your case, you can picture Personnel as contacts and Training Activities as Events.
The portal to the join table will only list training activities if you create a record in that portal's table (the join table) and link it to an activity. Take a look at the basic set up layout in the demo file. Create a new record and then click in the first row of the empty portal and select a value from the drop down list. This creates a record in the join table linking an event with a contact.
OK and thanks again Phil, I think I can take it from here.