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
|
|||
|
|||
when to use many-many relationships or different data bases
I am trying to create an operational database. We hire temporary staff
through several different employment agencies to complete work on projects for various clients. The term of employment is linked to individual projects which are time limited and include different assignments within each project. Many of the people we use have worked on many different projects at many different times including several years. I started out thinking I needed 5 different tables and needed to use a many-many relationship. Here are the 5 tables I identified with some types of data: Employee_Personal (usual type data) Employment_History (includes Dates hired, Projects assigned at different times, employment title per project, performance records; rehire status) Agency (related to each employee, # provided for each project; performance of employees provided) Project (Clients, Dates, subjects, teams needed, staff needed) Accounting [(Hours to complete project-administration pre training, training, execution and administrative client reporting); (staff cost factors computed for number of hours *title pay); (computer cost and needs per project); space cost and needs per project)] I started looking at the tables to try to see what relationships I needed and if I needed junction tables. I didn’t know how to handle the different dates of employment and different assignments for each employee and wondered if I could use multi-valued fields or value lists for this data. Then I started doubting if I was going in the right direction and thought I’d see if I could get any help. |
Thread Tools | |
Display Modes | |
|
|