Sounds like you have quite a situation.

Here is the best solution that I can come up with, from what I understand of
your situation.

You obviously need an Person table of some sort.

You need a MOS table

You need a Training table

and a linkage table between MOS and Training, because you are likely to have
multiple MOS's need the same training.

And just to throw a monkey wrench into the whole thing, you have some
training programs that apply not only to multiple MOS's, but may also apply
to multiple ranks.

My experience, when I was in the military, was that typically you couldn't
get promoted until you fulfilled all the previous requirements. But I wasn't
closely involved with the the Personal Actions office.

I would hate for your linkage table to end up needing the same MOS and the
only difference in the record is a rank attribute, but there shouldn't be any
reason to have a rank table. You could possibly use a multi-valued field to
store the rank(s).

"Jeff Boyce" wrote:

Kim

If I'm understanding your description, you want the completed training
information to follow the person AND their role/position, not just the
person. That would imply that you need to show Completed Training with:

TrainingID
PersonID
RoleID
... and other completed-training-related info

Are you doing this now?

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Kimberly3626" wrote in message
...
Yet again, I'm in way over my head! I'm going to simplify the current
situation to make it easy to understand (and communicate), and hopefully I
will be able to do what I intend to do without crashing everything that I
currently have!

I have a training management database. It pretty much automates my
position
for the guy taking my place. I have it set up to tie various training
requirements to the positions in the unit. The problem: Lets say someone
gets promoted. They move positions. As a result, all of the completed
training (tied to the position itself) must be reset to zero and
reentered.
In the event that they then move on to ANOTHER position where some of the
previous training now counts again, I have lost all record of that
original
training that they did in their first position. My solution: Tie the
training REQUIRED to the position. Then tie the COMPLETION DATA to the
individual!

Currently:
1. Table of personnel data. Unfortunately, being a military unit, SSN is
the PK. This table assigns a person to a position.
2. Table of Training. This ties the individual courses to the position.
Training ID is the PK. This includes the fields for 'Enrolled' and
'Completed.'
3. Tables are joined by relationships - one-to-many from the personnel
data
Position field to the training Position field.
This works outstanding! Aside from having to reinvent the wheel every
time
a person moves! (which happens more often than you'd think)

My Goal:
1. Table of Personnel Data. This still assigns the person to a position.
PK is still SSN. We'll call this table 'PD.'
2. Table of Required Training. This is designed the same as above, minus
the 'enrolled' and 'completed' fields. PK is Training ID. We'll call
this
table 'RD.'
(Note: My relationship - one-to-many from PDPosition and RTPosition works
great to generate what training is required for each position!)
3. Table of Completed Training. This table will include all of the
training
that an individual has completed throughout their lifetime on the team.
Not
all training will be required for all positions, but I don't want to lose
the
history of what they have accomplished. But this table is my nemesis!!!
PK
is Training ID (no relation to Table of Required Training's Training ID
field). We'll call this table 'CT.'

While I got the Query between tables 1 and 2 to work great, I need this
monstrosity to do the following:
Identify the position that a person is assigned to. Pull the required
training for that position. Then, pull the completed and enrolled data
for
ONLY the courses that are required for the position.
In short, a query design would look something like this: (which doesn't
work! It pulls all of the training, regardless of position, and assigns it
to
the person)
PD-SSN...PD-Position...RT-Course Title...CT-Enrolled...CT-Completed.

What I can't make it do: Ignore the extra training that a person has done
that is also in the CT table!

Thanks in advance.
Kim


.