My database

[charley]

I am currently building a database that holds a roster of employee names and
what their work activities are. This database will be available to each
person on the roster and allow them to apply data to each work activity.
What is the best way to organize the database to where each person on the
roster (204+) is able to input data against the database with each person
seeing same work activities. Do I need to create similar tables for each
person or is there a way to automatically duplicate the same table for each
person?

 

[Jeff Boyce]

Charley

"Step away from the database."

What you asked sounds like you have experience with spreadsheets.

But Access is a relational database. If you are considering duplicating
"the same table for each person", you need to revisit the topic of
normalization. You actually make your job harder to use Access' features if
you don't take advantage of relational design.

I'm not entirely clear on your situation, but will take a stab at it... You
have people (employees), you have work activities (?tote bale, lift barge,
drive railway spikes,...), and you have employees doing specific work
activities. If this is a reasonable paraphrase of your situation, you could
use something like:

tblEmployee
EmployeeID
FirstName
LastName
DateStarted
DateLeft

tblWorkActivity
WorkActivityID
Title
Description

trelEmployeeWorkActivity
EmployeeWorkActivityID
EmployeeID (from tblEmployee)
WorkActivityID (from tblWorkActivity)
DatePerformed

Or have I totally missed your point?

 

[charley]

Thanks Jeff, I am not totally versed in Access design so I have one more
question is this another table?:

trelEmployeeWorkActivity

 

[charley]

Also what do you mean by from tblEmployee and from tblWorkActivity

 

[Jeff Boyce]

Charley

I urge you to spend a bit of time looking into "normalization". The
concepts of "many-to-many", "primary and foreign key", and
"resolver/junction" tables need to be familiar, if not comfortable, if you
are going to get good use out of Access.

If you have neither time nor inclination to do a bit a study, you will find
that you will struggle to get Access to do what you've described so far --
it's kind of a "pay now or pay later" situation.

 

[Jim Davenport]

I am currently building a database that holds a roster of employee names and
what their work activities are. This database will be available to each
person on the roster and allow them to apply data to each work activity.
What is the best way to organize the database to where each person on the
roster (204+) is able to input data against the database with each person
seeing same work activities. Do I need to create similar tables for each
person or is there a way to automatically duplicate the same table for each
person?

Check out the Timesheets portion
of our application...

http://www.webshipments.com

Contact me for more info.