View Single Post
  #2  
Old September 24th, 2009, 10:12 PM posted to microsoft.public.access.tablesdbdesign
KARL DEWEY
external usenet poster
 
Posts: 10,767
Default Training Records Database

Suggestion - Do not use separate fields in instruction and employee tables to
indicate deparatments. Use another table.

Question - Do you have any re-occuring training such as Safety, Security,
Ethics, Sexual Harassment, etc? If so, then you need a field indicating
training cycle - annual (12 months), semiannual (6 months), quarterly (3
months), etc. Then you probably need training history (a separate record for
each time employee was trained on a given subject). Would you schedule based
upon last time trained or last time scheduled? Does everyone in a given
department require all training are do some, based on extra duties, need
subjects that others do not?

I was traing database manager for a 1000 employee organization and had a
query that created training records (employee-subject) for every topic of the
organization element they were assigned. A report was sent to the supervisor
to mark off any that was applicable to that person so the records could be
removed. In this way no one forgot to assigned any complusory training.

Any certifications required? We also recorded degrees and any speciality
training and skills even though not needed just in case the company might
have an immediate necessity.

--
Build a little, test a little.


"Jamie Dickerson" wrote:

I am trying to set up a database for employee training records. So far I
have set up the tables I will need:

Work Instructions : Lists all (200+) work instructions, which serve as our
main training tool, the document# serves as the primary key and 3 fields to
list the departments the work instruction relates to (most belong to more
than 1 dept. but no more than 3)

Employees: Employee # (primary key), name, and fields to list their relative
departments (all employees belong to multiple departments (up to 15).

Departments: List of departments with an autonumber field for primary key

Training Grid: Lists employee, document #, date trained and a hyperlink
field linking to a signautre sheet.

I would like to be able to create a report that shows who needs to be
trained based on the relative department and the documents assinged to it.
The problem I am running into is while the documents will only belong to up
to 3 departments, the employees may belong to all of them. The way the
tables are set up I cannot show this relationship. What would be a better
way to do this, if any? Any suggestions at this point would be helpful. I
consider myself an Access Novice so please keep any suggestions relatively
simple.