Table Structure
Table Structure
(OP)
Hello Everybody,
I need to create a performance appraisal Program. I have a table called "Employees" which contains all basic information about an employee. Each employee needs to be evaluated against 15 different Criterias and Grades ranging from A to E need to be assigned for each criteria. Finally i have to calculate the resultant Grade for each employee. I need some suggestions for the table structure and relationships. I am sure of the primary table employee. What about the new table for criteria? Each field name for each criteria or a single field name where you enter all the criterias and then assign that to the employee table in some sort of 1 to many relationships? How to assign the Grades? Please advise
Regards and Thanks
Charley
RE: Table Structure
That depends if the tests are going to be conducted more than once, if not this could be a 1 to optional 1 rel i guess not everyone will under go these tests (management usually think this isn't required for themselves ;- ) )
if the tests are going to be conducted more than once you need to have a 1 to M rel (obviously) i would have the EmpTests table list all the 15 criteria (unless there is some grouping of criteria/tests?) keeping the criteria items as seperate entities will allow easier access to individual criteria if required (and believe me this always comes up after the design of the database is finished,... like couldn't we just change this or that!)
Employee
EmpID ID Unique
OtherEmpData
.
.
--
Test
TestID ID Unique
OtherTestData 'date etc
.
.
--
Results
EmpID |E Employee.EmpID
TestID |E Test.TestID
Criteria1 1.1 ::= E{1,2,3,4,5}
Criteria2 ~
.
.
Criteria15 ~
this allows easy code based or query based processing of the criteria and form based data entry control.
setup "lookups" for the criteria either in the Results table or for the form with the waiting value as a hidden field 1 to 5 and display A to E for the users with what ever discriptions are needed
"1";"A";"Description..."
widths
0cm;1.0cm;Xcm (in know metric)
bound to col 1
Just an idea..
Robert Dwyer
rdwyer@orion-online.com.au