Hi Jori,

First you'll have to clarify a few things to yourself and us.

You indicated that you want to record individual requirements for training.
But yet you have a fair amount of discussion (and some structure) where
training requirements relate to titles and classes. As a subtler example,
your inclusion of a "frequency" field in your class table indicates that such
is an attribute of the class.

As a mental starting point for analysis, if your sole need is to record
requirements for training, in your mind (or on a copy) start by removing the
frequency field from classes, plus anything else that implies otherwise, and
make a new table (shorten my long name)
InstanceOfAClassAttendenceRequirementForAPerson. Two of the fields in it
will be the ID number of the person and the ID number of the class.

- - -

Now/or think about those other things that might reflect on those
requirements. For exam[ple, frequency of a class, information about Job
titles and title-dependent class requirements. What you wnat to do with
such information / considerations:

1. Leave it out of the database? In that case the "how to" is simple

2. Record it in the database, but just as general information that will
not trigger anything, it will just be "looked at" by people who will then
create training instance requirements in that new table. If so, just add
those fields

3. Have those considerations somehow automatically generate instances of
training requirements. If so, I would clarify excatly what those "rules"
are, and re-post in this group.

Hope that helps

Fred