View Single Post
  #5  
Old December 15th, 2009, 03:16 PM posted to microsoft.public.access.tablesdbdesign
Kimberly3626
external usenet poster
 
Posts: 26
Default Design Question. It works now...but how to redesign it?

Sorry for the delay...got stuck on a short notice trip!

First, I have really good news! I'm actually tracking training that is
position-specific and is completely independant of the rank and/or MOS of the
individual! We have some positions that are non-MOS specific...(As for the
Rank/MOS training, I can do that manually because we don't have many switches
between MOSs or Enlisted officer. As a result, I just load all of the
required training for your lifetime in one shot and check it off as you
complete it)

One example of what I'm dealing with:
Me! I was in Position A, which required Course A, Course B, and Course C.
I moved into Position B. This position requires Course A, Course C, and
Course D.

With the training tied to the position, the way it is now, when I move into
Position B, I have to not only clear the training data for the person who was
there before me, but I also have to enter all of my data from scratch. In
addition, I lose the database proof that I completed Course B. This is only
a problem because if we are certified in one position, we can cover it on our
own team or on another across the country. Without being able to pull the
certified personnel out of the DB, I lose the ability to cross-assign people
to meet a nationwide mission.

Seemingly not hard with the above example of 4 courses, but in reality, I
manage over 24,000 hours of training for the team that is completely position
dependant!

Looking at the replies, it seems like Karl's idea might work the best, minus
the Training Table (I'll only use the position training table for now). I'll
see what I can get to work, and let you all know what pops up...

If there are any more ideas that will work with the new 'simplified'
requirements, I'd love to hear em too! Not having the MOS wrench is a huge
help to the situation.

Thanks again!