Let's take employee training on as an example. Hopefully, you can use that example and apply it to listing training requirements for your clients as much the same implementation may be used.
Start with these relationships:
Employees::__pkEmployeeID = Employee_Course::_fkEmployeeID
Courses::__pkCourseID = Employee_Course::_fkCourseID
You can place a portal to Employee_Course on the Employees layout to list and select a Courses record for each given Employees record. Fields from Courses can be included in the Portal to show additional info about each selected Courses record and the _fkCourseID field can be set up with a value list for selecting Courses records by their ID field.
The follow demo file shows that method and others for matching up contacts with events in a many to many relationship. You can think of employees as contacts and events as courses:
Google "join tables filemaker"
Join my Table? – Part One
Join my Table? – Part Two
thanks guys. I'm going to study the example and check out the links you provided and try to tackle it again tomorrow. I'll let you know if I have any success. I truly appreciate the quick replies.