Design issue

[jmrobins]

I am trying to design a table in an existing database that keeps track of
employee evaluation dates/ratings. There are 2 evaluations due per year (mid
cycle and end cycle) and each has a rating. The issue is I'd like to keep
more than one year's worth of data on each person. How should I set up this
table in order to be able to keep multiple years of data?

 

[KARL DEWEY]

Use a datetime field or Year & Cycle fields.

 

[John W. Vinson]

I am trying to design a table in an existing database that keeps track of
employee evaluation dates/ratings. There are 2 evaluations due per year (mid
cycle and end cycle) and each has a rating. The issue is I'd like to keep
more than one year's worth of data on each person. How should I set up this
table in order to be able to keep multiple years of data?

You need (at least) two tables: an Employees table related one to many to a
Ratings table. The Employees table would contain biographical and job data,
but nothing about ratings; the Ratings table would contain as many records for
each employee as that employee has had evaluations.

John W. Vinson [MVP]