How do I specify project leaders within a list of employees?

Project leaders receive the same per piece pay as employees but receive a
stipend.
How can I set up my Access database to accommodate the stipend?

You could add a field to your employee table that designates who is a project
leader, and then use that field in your calculation of payment. If you only
have normal employees and project leaders, the field could be a boolean
(Yes/No) indicating a project leader.

"Alice at VP" wrote:

Project leaders receive the same per piece pay as employees but receive a
stipend.
How can I set up my Access database to accommodate the stipend?

Thank you. I'll give it a shot


"mnature" wrote:

You could add a field to your employee table that designates who is a project
leader, and then use that field in your calculation of payment. If you only
have normal employees and project leaders, the field could be a boolean
(Yes/No) indicating a project leader.

"Alice at VP" wrote:

Project leaders receive the same per piece pay as employees but receive a
stipend.
How can I set up my Access database to accommodate the stipend?

Ok. I did that and it did separate my team leaders on the list. However, it
put the stipend (which should only be a one time per report) for all of the
records for the team leaders and for all of the employees. Here's what I'm
going for:
Name Pieces @rate Stipend Total
Leader 25 $25.00 $100.00 $125.00
Leader 10 $10.00 $100.00 $110.00
Employee 25 $25.00 $ 25.00
Employee 50 $50.00 $ 50.00

How can I do that?

"mnature" wrote:

You could add a field to your employee table that designates who is a project
leader, and then use that field in your calculation of payment. If you only
have normal employees and project leaders, the field could be a boolean
(Yes/No) indicating a project leader.

"Alice at VP" wrote:

Project leaders receive the same per piece pay as employees but receive a
stipend.
How can I set up my Access database to accommodate the stipend?

Personally, I would /not/ add a field to the employees record to
designate the project leaders. What if the same person is project
leader for project 'A', but a simple team member for project 'B'? Even
if that wouldn't occur, yet, in your organization, I say you should do
this properly from the beginning.

A person's role, on some project, is not an attribute (or characterist)
of the person alone; the same person might have diferent roles in
different projects. So it can't go in the persons table.

Similarly, it is not an attribute of the project alone; the project
might have many people, each one with a different role. So it can't go
in the Projects table.

It is actually an attribute of the /combination/ of person and project.
So it needs to go in a joining table between person and project. Then,
the same person can have different roles in different projects, and
conversely, a project can have many people each one with a different
role.

(using my own table & field names, just to make it easy for me)

tblPerson
PersonID primary key
name, adrs, date of birth, etc.

tblProject
ProjectID primay key
title, sponsor, date started, etc.

tblProjectMember
ProjectID composite
PersonID primary key
role (worker, project manager, auditor, etc.)

HTH,
TC [MVP Access]

Thanks. This should help. Actually, you hit the nail on the head. We have
one person who is team leader on two projects, one person who is team leader
on one project and a regular employee on another project. I'll let you know
how this works out.

"TC" wrote:

Personally, I would /not/ add a field to the employees record to
designate the project leaders. What if the same person is project
leader for project 'A', but a simple team member for project 'B'? Even
if that wouldn't occur, yet, in your organization, I say you should do
this properly from the beginning.

A person's role, on some project, is not an attribute (or characterist)
of the person alone; the same person might have diferent roles in
different projects. So it can't go in the persons table.

Similarly, it is not an attribute of the project alone; the project
might have many people, each one with a different role. So it can't go
in the Projects table.

It is actually an attribute of the /combination/ of person and project.
So it needs to go in a joining table between person and project. Then,
the same person can have different roles in different projects, and
conversely, a project can have many people each one with a different
role.

(using my own table & field names, just to make it easy for me)

tblPerson
PersonID primary key
name, adrs, date of birth, etc.

tblProject
ProjectID primay key
title, sponsor, date started, etc.

tblProjectMember
ProjectID composite
PersonID primary key
role (worker, project manager, auditor, etc.)

HTH,
TC [MVP Access]