G
Guest
I am attempting to design a database that will track Employees Training. My
situation is a little bit complex because the training courses are revised
frequently, and they are split into two sections; day(bpr1) one and day(bpr2)
two. Let's say Each section consists of twelve modules. The Day one
section has a specially designated number, so does the Day two section. Both
sections are represented by a Batch Number. So far I have create three
tables. One for the Lot Number with the following fields : Lot Number; BPR1,
and BPR2, Employee training table (junction Table) with the following
fields, EmpID, LastName, FirstName, and Lot Number, and a finally a section
Table that lists all twelve modules, description field for each module and
the current version of each module (they are frequently revised., also an
employee needs to be trained, once a module is revised.
My problem is figuring out how to link the tables without causing repetitive
data occurance.
situation is a little bit complex because the training courses are revised
frequently, and they are split into two sections; day(bpr1) one and day(bpr2)
two. Let's say Each section consists of twelve modules. The Day one
section has a specially designated number, so does the Day two section. Both
sections are represented by a Batch Number. So far I have create three
tables. One for the Lot Number with the following fields : Lot Number; BPR1,
and BPR2, Employee training table (junction Table) with the following
fields, EmpID, LastName, FirstName, and Lot Number, and a finally a section
Table that lists all twelve modules, description field for each module and
the current version of each module (they are frequently revised., also an
employee needs to be trained, once a module is revised.
My problem is figuring out how to link the tables without causing repetitive
data occurance.