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
|
|||
|
|||
Help with table setup for many-to-many/categories
I want to set up a database of my work experience. I think it will be useful
in pulling different job skills and accomplishments to help me in configuring a resume to a specific job. I also thought it would be useful as an exercise to brush up on long dormant skills. If my being as stuck as I am now is any indication, I think they are long dead skills, not dormant. I would appreciate help in how to set up the tables. Here's what I have so far: Table One - Jobs Company Name Job Title Start Date End Date Supervisor Supervisor extension Table Two - Companies Company Name Address City State Zip Phone URL Notes Table Three - Accomplishments Accomplishment Detail Table Four - Skills Skill Category Table Five - Junction Table primary key accomplishments primary key skills Each job has a list of accomplishments that can be categorized into one or more skill categories. If I write general accomplishments (like supervising people), they can relate to more than one job. Ultimately I want to be able to pull a list of all jobs that relate to certain skills, all accomplishments that relate to certain skills, and all accomplishments related to a certain job. I'm just not sure how to apply more than one category to an accomplishment. I understand (vaguley) the concept of building a junction table with the primary key from both the accomplishment and skills tables, but my head starts to hurt after that. Any words of wisdom to get me headed in the right direction would be GREATLY APPRECIATED!! Thanks |
#2
|
|||
|
|||
Help with table setup for many-to-many/categories
suggest you read up on relational design, until you can recategorize your
understanding of junction tables from vague to clear. g seriously, properly structured tables/relationships are the root of your entire database (of any relational database), so i really do recommend that you read up on the subject until you're comfortable with it. for more information, see http://www.accessmvp.com/JConrad/acc...abaseDesign101 hth "debl5" u51915@uwe wrote in message news:9615a21ac6b58@uwe... I want to set up a database of my work experience. I think it will be useful in pulling different job skills and accomplishments to help me in configuring a resume to a specific job. I also thought it would be useful as an exercise to brush up on long dormant skills. If my being as stuck as I am now is any indication, I think they are long dead skills, not dormant. I would appreciate help in how to set up the tables. Here's what I have so far: Table One - Jobs Company Name Job Title Start Date End Date Supervisor Supervisor extension Table Two - Companies Company Name Address City State Zip Phone URL Notes Table Three - Accomplishments Accomplishment Detail Table Four - Skills Skill Category Table Five - Junction Table primary key accomplishments primary key skills Each job has a list of accomplishments that can be categorized into one or more skill categories. If I write general accomplishments (like supervising people), they can relate to more than one job. Ultimately I want to be able to pull a list of all jobs that relate to certain skills, all accomplishments that relate to certain skills, and all accomplishments related to a certain job. I'm just not sure how to apply more than one category to an accomplishment. I understand (vaguley) the concept of building a junction table with the primary key from both the accomplishment and skills tables, but my head starts to hurt after that. Any words of wisdom to get me headed in the right direction would be GREATLY APPRECIATED!! Thanks |
#3
|
|||
|
|||
Help with table setup for many-to-many/categories
Thanks for the suggestion and links.
tina wrote: suggest you read up on relational design, until you can recategorize your understanding of junction tables from vague to clear. g seriously, properly structured tables/relationships are the root of your entire database (of any relational database), so i really do recommend that you read up on the subject until you're comfortable with it. for more information, see http://www.accessmvp.com/JConrad/acc...abaseDesign101 hth I want to set up a database of my work experience. I think it will be useful in pulling different job skills and accomplishments to help me in configuring [quoted text clipped - 49 lines] APPRECIATED!! Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200905/1 |
#4
|
|||
|
|||
Help with table setup for many-to-many/categories
you're welcome
"debl5 via AccessMonster.com" u51915@uwe wrote in message news:961d06ed2db08@uwe... Thanks for the suggestion and links. tina wrote: suggest you read up on relational design, until you can recategorize your understanding of junction tables from vague to clear. g seriously, properly structured tables/relationships are the root of your entire database (of any relational database), so i really do recommend that you read up on the subject until you're comfortable with it. for more information, see http://www.accessmvp.com/JConrad/acc...DatabaseDesign 101 hth I want to set up a database of my work experience. I think it will be useful in pulling different job skills and accomplishments to help me in configuring [quoted text clipped - 49 lines] APPRECIATED!! Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200905/1 |
Thread Tools | |
Display Modes | |
|
|