database setup fields

[Ninamashr]

I am creating a simple "Training" database for my company. We would like to track employees and departments that need training. We are planning the following fields, Employee name, Department, Training Type, Date training planned, Date training completed, We would also like to run reports on employees that have training scheduled but not completed.

I'm not sure how to set it up, whether or not I should be using repeating fields, etc; we have about 20 different training types, and about 5 different departments. We only need a report to display the training not completed per employee, and I can't figure out how to display the training not completed in the date repeating fields.

Thanks for your help

[Vaughan]

Do NOT use repeating fields. Do it relationally. The learning curve might initially be a bit steeper for relational, but in the end it'll be much, much better.

Your basic structure will be:

Employees table

Enrolments table

Session table

Course table

The Session table is so you can run a "course" more than once -- the session is a course run at a particular time or place (you could also add a Locations table and an Instructors table that link into Sessions as well).

(People usually only find that repeating fields suck when they try to generate reports, and then discover that the data isn't easy to get to.)

[Genx]

much, much better.

Add two more much's there!!