file review dbase

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ced - 16 Jul 2006 20:39 GMT

I am trying to create a dbase for employee file reviews. On paper each
review, lists: the employee, manager, district, file #, date of incident,
customer name and 25 yes/no questions. How would I go about creating a proper
table structure for this dbase? Each employee will have an almost infinite
number of files reviewed. The same goes for the manager reviewing the files.
The purpose for this dbase is to keep track of what employees are missing in
their files. Where they can be listed in reports. Thanks for any assistance
you can provide.

Reply to this Message

John Spencer - 17 Jul 2006 13:17 GMT

I would probably have at least the following tables.
EmployeeTable (for employees and managers)
--EmployeeID
--EmployeeLastName
--EmployeeFirstName
--ManagerID (Reference to an EmployeeID)
CustomerTable
--CustomerID
--CustomerName
--(Other information on customer)
QuestionsTable (This would just list the 25 yes/no questions)
--QuestionID
--QuestionText
ReviewTable
--ReviewID
--FileNumber
--IncidentDate
Responses
--ReviewID
--QuestionID
--Response

You need to analyze your table structure to decide if more items are needed
in each table and you need to decide if there are other entities that need
to be tracked.

>I am trying to create a dbase for employee file reviews. On paper each
> review, lists: the employee, manager, district, file #, date of incident,
[quoted text clipped - 8 lines]
> assistance
> you can provide.

Reply to this Message