If i do the following, will this make a form for each employee or will it make one for all?
Sorry this post is part of another thread
You're on the right track. Make an Employees table with just employee data. Make a Tasks table with just task information. Each of these will have a primary key; EmployeeID, TaskID (both AutoNumber).
to assign and track tasks, build an Assignments table with at least these fields:
AssignmentID (primary key, Autonumber)
EmployeeID (Number)
TaskID (Number)
In Relationships view, join Employees to Assignments on EmployeeID, and enforce referential integrity. Also join Tasks to Assignments on TaskID and enforce referential integrity.
The Assignments table can have other fields directly related to the assignment; AssignedDate (Date/Time)
CompletedDate (Date/Time)
AssignmentNotes (Memo)
...and maybe some others that you can think of.
Data entry --
Build frmEmployees, based on the Employees table. Single record per page.
Build sfmAssignments, based on the Assignments table. Datasheet view.
In Design view on frmEmployees, press F11 to bring the database container to teh front. Drag the sfmAssignments table onto frmEmployees, and let go.
IMMEDIATELY click the Properties button, go to the Data tab, and check to see that the Master and Child fields are populated. They should both be EmployeeID -- enter the field names if they are blank.
Take a look. You will see a Datasheet view where any tasks you enter in the subform will be asssigned to the current employee. You can (and should) make your life easier by modifying the subform so that the TaskID field is a combo box, not a text box. This wll let your users pick a task description, while storing just the ID for later use.
Down the track you can build queries around the Assignments table, for reporting on employees by task, tasks by employee, and a range of other stuff.
Sorry this post is part of another thread
You're on the right track. Make an Employees table with just employee data. Make a Tasks table with just task information. Each of these will have a primary key; EmployeeID, TaskID (both AutoNumber).
to assign and track tasks, build an Assignments table with at least these fields:
AssignmentID (primary key, Autonumber)
EmployeeID (Number)
TaskID (Number)
In Relationships view, join Employees to Assignments on EmployeeID, and enforce referential integrity. Also join Tasks to Assignments on TaskID and enforce referential integrity.
The Assignments table can have other fields directly related to the assignment; AssignedDate (Date/Time)
CompletedDate (Date/Time)
AssignmentNotes (Memo)
...and maybe some others that you can think of.
Data entry --
Build frmEmployees, based on the Employees table. Single record per page.
Build sfmAssignments, based on the Assignments table. Datasheet view.
In Design view on frmEmployees, press F11 to bring the database container to teh front. Drag the sfmAssignments table onto frmEmployees, and let go.
IMMEDIATELY click the Properties button, go to the Data tab, and check to see that the Master and Child fields are populated. They should both be EmployeeID -- enter the field names if they are blank.
Take a look. You will see a Datasheet view where any tasks you enter in the subform will be asssigned to the current employee. You can (and should) make your life easier by modifying the subform so that the TaskID field is a combo box, not a text box. This wll let your users pick a task description, while storing just the ID for later use.
Down the track you can build queries around the Assignments table, for reporting on employees by task, tasks by employee, and a range of other stuff.