If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Work Areas in a database
I am working on a new database to keep track of our department employees demographics as well as other things. Right now we keep track of their work areas in an excel spreadsheet. I want to know if it would be a good idea to try to incorporate the work areas in my database since it keeps track of seniority, name changes, etc better than excel. We keep track of the number of hours each employee works in each area. There are 8 work areas. I have a separate sheet for each area and the supervisor types in the number of hours each employee worked in a particular area on a particular date.
On my final report page in excel it lists the day shift employees from the most senior to the least senior in column A. Column B are the totals for a work area, Column C are the totals for the second work area and so on to show all 8 work areas and total number of hours worked in each area for each employee all on one sheet. If I put these work areas in access, would I create a separate table for each work area and link by EmployeeID and then join all the tables in a query to make the report or would I make one table called work areas and have a WorkAreaID, EmployeeID, WorkArea, WorkAreaDate, WorkAreaHours? Thanks, Linda |
#2
|
|||
|
|||
It is seldom a good idea to create multiple tables to represent the same
entity. You invariably end up naming the tables in such a way that the table name actually contains data in it (WorkArea1, WorkArea2 and so on), making it very difficult to do effective searches. Your second approach would be much better. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (No private e-mails, please) "LMB" wrote in message ... I am working on a new database to keep track of our department employees demographics as well as other things. Right now we keep track of their work areas in an excel spreadsheet. I want to know if it would be a good idea to try to incorporate the work areas in my database since it keeps track of seniority, name changes, etc better than excel. We keep track of the number of hours each employee works in each area. There are 8 work areas. I have a separate sheet for each area and the supervisor types in the number of hours each employee worked in a particular area on a particular date. On my final report page in excel it lists the day shift employees from the most senior to the least senior in column A. Column B are the totals for a work area, Column C are the totals for the second work area and so on to show all 8 work areas and total number of hours worked in each area for each employee all on one sheet. If I put these work areas in access, would I create a separate table for each work area and link by EmployeeID and then join all the tables in a query to make the report or would I make one table called work areas and have a WorkAreaID, EmployeeID, WorkArea, WorkAreaDate, WorkAreaHours? Thanks, Linda |
#3
|
|||
|
|||
Thanks,
I wasn't sure if I would need 3 tables to do this. Employees, Junction, Work Areas. Would it be a many to many relationship? Many employees work many areas or is the way I have it going to work? I keep trying to get this on paper so I can see how the data willl look but I probably need to do something else for a little while. Thanks, Linda "Douglas J. Steele" wrote in message ... It is seldom a good idea to create multiple tables to represent the same entity. You invariably end up naming the tables in such a way that the table name actually contains data in it (WorkArea1, WorkArea2 and so on), making it very difficult to do effective searches. Your second approach would be much better. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (No private e-mails, please) "LMB" wrote in message ... I am working on a new database to keep track of our department employees demographics as well as other things. Right now we keep track of their work areas in an excel spreadsheet. I want to know if it would be a good idea to try to incorporate the work areas in my database since it keeps track of seniority, name changes, etc better than excel. We keep track of the number of hours each employee works in each area. There are 8 work areas. I have a separate sheet for each area and the supervisor types in the number of hours each employee worked in a particular area on a particular date. On my final report page in excel it lists the day shift employees from the most senior to the least senior in column A. Column B are the totals for a work area, Column C are the totals for the second work area and so on to show all 8 work areas and total number of hours worked in each area for each employee all on one sheet. If I put these work areas in access, would I create a separate table for each work area and link by EmployeeID and then join all the tables in a query to make the report or would I make one table called work areas and have a WorkAreaID, EmployeeID, WorkArea, WorkAreaDate, WorkAreaHours? Thanks, Linda |
#4
|
|||
|
|||
Yeah, you're probably best off assuming it's a many-to-many relationship,
with a Junction table to resolve the many-to-many. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "LMB" wrote in message ... Thanks, I wasn't sure if I would need 3 tables to do this. Employees, Junction, Work Areas. Would it be a many to many relationship? Many employees work many areas or is the way I have it going to work? I keep trying to get this on paper so I can see how the data willl look but I probably need to do something else for a little while. Thanks, Linda "Douglas J. Steele" wrote in message ... It is seldom a good idea to create multiple tables to represent the same entity. You invariably end up naming the tables in such a way that the table name actually contains data in it (WorkArea1, WorkArea2 and so on), making it very difficult to do effective searches. Your second approach would be much better. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (No private e-mails, please) "LMB" wrote in message ... I am working on a new database to keep track of our department employees demographics as well as other things. Right now we keep track of their work areas in an excel spreadsheet. I want to know if it would be a good idea to try to incorporate the work areas in my database since it keeps track of seniority, name changes, etc better than excel. We keep track of the number of hours each employee works in each area. There are 8 work areas. I have a separate sheet for each area and the supervisor types in the number of hours each employee worked in a particular area on a particular date. On my final report page in excel it lists the day shift employees from the most senior to the least senior in column A. Column B are the totals for a work area, Column C are the totals for the second work area and so on to show all 8 work areas and total number of hours worked in each area for each employee all on one sheet. If I put these work areas in access, would I create a separate table for each work area and link by EmployeeID and then join all the tables in a query to make the report or would I make one table called work areas and have a WorkAreaID, EmployeeID, WorkArea, WorkAreaDate, WorkAreaHours? Thanks, Linda |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can I move the MDW file? | Damien McBain | General Discussion | 7 | September 28th, 2004 09:54 AM |
Adding staff photographs to my database | KK | New Users | 2 | September 3rd, 2004 07:41 AM |
Upload Image | Jason MacKenzie | General Discussion | 1 | September 1st, 2004 04:38 AM |
Need help: Can't create ADP Database in MSDE from MS Access | Lou Arnold | General Discussion | 0 | July 21st, 2004 04:54 AM |
Label | SRIT | General Discussion | 2 | June 22nd, 2004 09:42 PM |