|
| 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
July 2nd, 2009, 08:29 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
New Db Setup Tables/Forms
I'm setting up a new database for all of the projects that I have and
subsequently I need to track the employees involved with each project. I started out creating a table of employees (( Empl ID (Primary), Fr Name, Lst Name, Title, Function, Manager, Pay Rate.)) Then I created a table for the projects ((Proj ID (Primary), Description, Type, Proj Value, Begin and End Proj Dates )) That was easy, then I had to create a table for each project that shows (Empl ID, Hours Budgeted, Hours Worked, Hours Available )) - I have 32 of these tables. I had to (i think) because I can have one employee working on 15 different projects. I want to create a single form that populates the Project Tables. I want to have something like a pull down menu that I can select the Project from and update it monthly. But I cannot get all of these tables to load to a single form. Can someone give me some direction here?? 
|
|
#2
July 2nd, 2009, 08:56 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
New Db Setup Tables/Forms
One table for each project, ... hmmm ... that sounds like a ... spreadsheet!
Access is a relational database. If you feed it 'sheet data, you won't get very good use of its relationally-oriented features/functions. In fact, both you and Access will have to work overtime to come up with work-arounds (i.e., kludges) to try to get things done Access isn't designed to do. You can pay now (learn about relational database design and normalization, then apply it to make your data well-normalized), or you can pay later (every time you need to start a new project with your design, you'll have to modify your tables, forms, queries, reports, etc.). Good luck! Regards Jeff Boyce Microsoft Office/Access MVP "BKC468" u52984@uwe wrote in message news:987c591345430@uwe... I'm setting up a new database for all of the projects that I have and subsequently I need to track the employees involved with each project. I started out creating a table of employees (( Empl ID (Primary), Fr Name, Lst Name, Title, Function, Manager, Pay Rate.)) Then I created a table for the projects ((Proj ID (Primary), Description, Type, Proj Value, Begin and End Proj Dates )) That was easy, then I had to create a table for each project that shows (Empl ID, Hours Budgeted, Hours Worked, Hours Available )) - I have 32 of these tables. I had to (i think) because I can have one employee working on 15 different projects. I want to create a single form that populates the Project Tables. I want to have something like a pull down menu that I can select the Project from and update it monthly. But I cannot get all of these tables to load to a single form. Can someone give me some direction here??
|
|
#3
July 2nd, 2009, 09:17 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
New Db Setup Tables/Forms
I know, I know but there are so many projects and one employee can be a part
of multiple projects. I've pulled some relational information to paroose again over the weekend. I'll try again to rebuild the tables which is what I know I need to do. Jeff Boyce wrote: One table for each project, ... hmmm ... that sounds like a ... spreadsheet! You can pay now (learn about relational database design and normalization, then apply it to make your data well-normalized), or you can pay later (every time you need to start a new project with your design, you'll have to modify your tables, forms, queries, reports, etc.). Good luck! Regards Jeff Boyce Microsoft Office/Access MVP I'm setting up a new database for all of the projects that I have and subsequently I need to track the employees involved with each project. [quoted text clipped - 18 lines] single form. Can someone give me some direction here??
|
|
#4
July 2nd, 2009, 10:59 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
New Db Setup Tables/Forms
Consider the following ... (I'm guessing that your projects are similar to
mine...) tblProject ProjectID ProjectTitle Project Description ... (other project-specific attributes) tblEmployee EmployeeID FName LName ... (other employee-specific attributes) trelAssignment AssignmentID EmployeeID ProjectID FromDate ToDate This approach lets you assign one employee to many projects and many employees to one project. Good luck! Regards Jeff Boyce Microsoft Office/Access MVP "BKC468" u52984@uwe wrote in message news:987cc46151188@uwe... I know, I know but there are so many projects and one employee can be a part of multiple projects. I've pulled some relational information to paroose again over the weekend. I'll try again to rebuild the tables which is what I know I need to do. Jeff Boyce wrote: One table for each project, ... hmmm ... that sounds like a ... spreadsheet! You can pay now (learn about relational database design and normalization, then apply it to make your data well-normalized), or you can pay later (every time you need to start a new project with your design, you'll have to modify your tables, forms, queries, reports, etc.). Good luck! Regards Jeff Boyce Microsoft Office/Access MVP I'm setting up a new database for all of the projects that I have and subsequently I need to track the employees involved with each project. [quoted text clipped - 18 lines] single form. Can someone give me some direction here??
|
|
#5
July 3rd, 2009, 02:37 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
New Db Setup Tables/Forms
aha, Jeff, so you're the one who helped my boss figure out how to give me 17
things to do at once! g "Jeff Boyce" wrote in message ... Consider the following ... (I'm guessing that your projects are similar to mine...) tblProject ProjectID ProjectTitle Project Description ... (other project-specific attributes) tblEmployee EmployeeID FName LName ... (other employee-specific attributes) trelAssignment AssignmentID EmployeeID ProjectID FromDate ToDate This approach lets you assign one employee to many projects and many employees to one project. Good luck! Regards Jeff Boyce Microsoft Office/Access MVP "BKC468" u52984@uwe wrote in message news:987cc46151188@uwe... I know, I know but there are so many projects and one employee can be a part of multiple projects. I've pulled some relational information to paroose again over the weekend. I'll try again to rebuild the tables which is what I know I need to do. Jeff Boyce wrote: One table for each project, ... hmmm ... that sounds like a ... spreadsheet! You can pay now (learn about relational database design and normalization, then apply it to make your data well-normalized), or you can pay later (every time you need to start a new project with your design, you'll have to modify your tables, forms, queries, reports, etc.). Good luck! Regards Jeff Boyce Microsoft Office/Access MVP I'm setting up a new database for all of the projects that I have and subsequently I need to track the employees involved with each project. [quoted text clipped - 18 lines] single form. Can someone give me some direction here??
|
|
#6
July 6th, 2009, 01:58 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
New Db Setup Tables/Forms
Thanks Jeff - I can tweek the empl and project table to get this, but can you
tell me what you are emplying by TrelEmployee? Did you mean Table? Jeff Boyce wrote: Consider the following ... (I'm guessing that your projects are similar to mine...) tblProject ProjectID ProjectTitle Project Description ... (other project-specific attributes) tblEmployee EmployeeID FName LName ... (other employee-specific attributes) trelAssignment AssignmentID EmployeeID ProjectID FromDate ToDate This approach lets you assign one employee to many projects and many employees to one project. Good luck! Regards Jeff Boyce Microsoft Office/Access MVP I know, I know but there are so many projects and one employee can be a part [quoted text clipped - 25 lines] single form. Can someone give me some direction here?? -- Message posted via http://www.accessmonster.com
|
|
#7
July 6th, 2009, 04:31 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
New Db Setup Tables/Forms
many-to-many, doncha just love it?!
Regards Jeff Boyce Microsoft Office/Access MVP "tina" wrote in message ... aha, Jeff, so you're the one who helped my boss figure out how to give me 17 things to do at once! g "Jeff Boyce" wrote in message ... Consider the following ... (I'm guessing that your projects are similar to mine...) tblProject ProjectID ProjectTitle Project Description ... (other project-specific attributes) tblEmployee EmployeeID FName LName ... (other employee-specific attributes) trelAssignment AssignmentID EmployeeID ProjectID FromDate ToDate This approach lets you assign one employee to many projects and many employees to one project. Good luck! Regards Jeff Boyce Microsoft Office/Access MVP "BKC468" u52984@uwe wrote in message news:987cc46151188@uwe... I know, I know but there are so many projects and one employee can be a part of multiple projects. I've pulled some relational information to paroose again over the weekend. I'll try again to rebuild the tables which is what I know I need to do. Jeff Boyce wrote: One table for each project, ... hmmm ... that sounds like a ... spreadsheet! You can pay now (learn about relational database design and normalization, then apply it to make your data well-normalized), or you can pay later (every time you need to start a new project with your design, you'll have to modify your tables, forms, queries, reports, etc.). Good luck! Regards Jeff Boyce Microsoft Office/Access MVP I'm setting up a new database for all of the projects that I have and subsequently I need to track the employees involved with each project. [quoted text clipped - 18 lines] single form. Can someone give me some direction here??
|
|
#8
July 6th, 2009, 04:32 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
New Db Setup Tables/Forms
Sorry, I used a prefix that usually stands for "table-relationship" (AKA,
junction table, resolver table). These are used to handle many-to-many relationships (and if an employee can work on many projects ... over time .... and a project can have many employees working on it, you have a many-to-many relationship). Regards Jeff Boyce Microsoft Office/Access MVP "BKC468 via AccessMonster.com" u52984@uwe wrote in message news:98ab3b4a94655@uwe... Thanks Jeff - I can tweek the empl and project table to get this, but can you tell me what you are emplying by TrelEmployee? Did you mean Table? Jeff Boyce wrote: Consider the following ... (I'm guessing that your projects are similar to mine...) tblProject ProjectID ProjectTitle Project Description ... (other project-specific attributes) tblEmployee EmployeeID FName LName ... (other employee-specific attributes) trelAssignment AssignmentID EmployeeID ProjectID FromDate ToDate This approach lets you assign one employee to many projects and many employees to one project. Good luck! Regards Jeff Boyce Microsoft Office/Access MVP I know, I know but there are so many projects and one employee can be a part [quoted text clipped - 25 lines] single form. Can someone give me some direction here?? -- Message posted via http://www.accessmonster.com
|
|
#9
July 6th, 2009, 05:05 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
New Db Setup Tables/Forms
Thank you so much, I think this work. I will reply to you again when I have
finished loading the information to say thank you!! Jeff Boyce wrote: Sorry, I used a prefix that usually stands for "table-relationship" (AKA, junction table, resolver table). These are used to handle many-to-many relationships (and if an employee can work on many projects ... over time ... and a project can have many employees working on it, you have a many-to-many relationship). Regards Jeff Boyce Microsoft Office/Access MVP Thanks Jeff - I can tweek the empl and project table to get this, but can you [quoted text clipped - 37 lines] single form. Can someone give me some direction here?? -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200907/1
|
|
#10
July 7th, 2009, 02:12 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
New Db Setup Tables/Forms
well, from a design standpoint, yeah - but from a work standpoint, not so
much! on the other hand, in this economy i'm grateful to have a job at all, so i'll do my 17 tasks and keep my mouth shut!  "Jeff Boyce" wrote in message ... many-to-many, doncha just love it?! Regards Jeff Boyce Microsoft Office/Access MVP "tina" wrote in message ... aha, Jeff, so you're the one who helped my boss figure out how to give me 17 things to do at once! g "Jeff Boyce" wrote in message ... Consider the following ... (I'm guessing that your projects are similar to mine...) tblProject ProjectID ProjectTitle Project Description ... (other project-specific attributes) tblEmployee EmployeeID FName LName ... (other employee-specific attributes) trelAssignment AssignmentID EmployeeID ProjectID FromDate ToDate This approach lets you assign one employee to many projects and many employees to one project. Good luck! Regards Jeff Boyce Microsoft Office/Access MVP "BKC468" u52984@uwe wrote in message news:987cc46151188@uwe... I know, I know but there are so many projects and one employee can be a part of multiple projects. I've pulled some relational information to paroose again over the weekend. I'll try again to rebuild the tables which is what I know I need to do. Jeff Boyce wrote: One table for each project, ... hmmm ... that sounds like a ... spreadsheet! You can pay now (learn about relational database design and normalization, then apply it to make your data well-normalized), or you can pay later (every time you need to start a new project with your design, you'll have to modify your tables, forms, queries, reports, etc.). Good luck! Regards Jeff Boyce Microsoft Office/Access MVP I'm setting up a new database for all of the projects that I have and subsequently I need to track the employees involved with each project. [quoted text clipped - 18 lines] single form. Can someone give me some direction here??
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
