Help in Creating Relationships in a table
in [Getting Started]
|
Prev: subforms: using input from one subform to update the other subform
Next: subforms: using input from one subform to update the other sub
From: forest8 on 5 Apr 2010 12:02 Hi This is a follow to a previous question concerning relationships in a table. These are my tables I have in my database. Students StudentsID LastName FirstName HomeroomTeacher (ohter info relating to the student) Cases CaseNo_ID <PK> StudentID <FK> Categories CategoryID <PK> Category (e.g. School, Community, Individual, Peers, Family) Issues IssuesID <PK> Issues (text, e.g. lack of role models) CategoryID <FK> StudentIssues CaseNoID <link to Cases Table> IssuesID <Link to issues Table> Actions ActionsID <PK> Actions (text, eg. New Adult Role Models) CategoryID <FK> StudentActions CaseNoID <link to Cases Table> ActionsID <link to Actions Table> Does this look right to anyone? Is it possible to merge the Actions and Issues tables together or is it best to leave them separate? Thank you in advance for your help
From: Dorian on 5 Apr 2010 15:06 > Is it possible to merge the Actions and Issues tables together or is it best > to leave them separate? Not if an issue can have more than one action. Also you have issues and actions both linked to category, what is the purpose of category? Might you not have different subsets of categories for issues and actions? -- Dorian "Give someone a fish and they eat for a day; teach someone to fish and they eat for a lifetime". "forest8" wrote: > Hi > > This is a follow to a previous question concerning relationships in a table. > > These are my tables I have in my database. > > Students > StudentsID > LastName > FirstName > HomeroomTeacher > (ohter info relating to the student) > > Cases > CaseNo_ID <PK> > StudentID <FK> > > Categories > CategoryID <PK> > Category (e.g. School, Community, Individual, Peers, Family) > > Issues > IssuesID <PK> > Issues (text, e.g. lack of role models) > CategoryID <FK> > > StudentIssues > CaseNoID <link to Cases Table> > IssuesID <Link to issues Table> > > Actions > ActionsID <PK> > Actions (text, eg. New Adult Role Models) > CategoryID <FK> > > StudentActions > CaseNoID <link to Cases Table> > ActionsID <link to Actions Table> > > Does this look right to anyone? > > Is it possible to merge the Actions and Issues tables together or is it best > to leave them separate? > > Thank you in advance for your help >
From: forest8 on 5 Apr 2010 18:16 Hi there All the issues and actions are tied to a category. An Issue can have more than 1 action. For instance, if a student has no role model in his family, then a possible action is to develop a positive role model, [Category: Family, Issue: Lack of Role Model; Action: Develop Adult role models] Several issues may have the same action. For instance, a youth has no adult role models and has a poor relationship with his family, then the action is to develop a positive role model. [Category: Family, Family. Issue: Lack of Role Model, Action: Develop adult role model] Does this make sense? Thanks "Dorian" wrote: > > Is it possible to merge the Actions and Issues tables together or is it best > > to leave them separate? > Not if an issue can have more than one action. > Also you have issues and actions both linked to category, what is the > purpose of category? Might you not have different subsets of categories for > issues and actions? > -- Dorian > "Give someone a fish and they eat for a day; teach someone to fish and they > eat for a lifetime". > > > "forest8" wrote: > > > Hi > > > > This is a follow to a previous question concerning relationships in a table. > > > > These are my tables I have in my database. > > > > Students > > StudentsID > > LastName > > FirstName > > HomeroomTeacher > > (ohter info relating to the student) > > > > Cases > > CaseNo_ID <PK> > > StudentID <FK> > > > > Categories > > CategoryID <PK> > > Category (e.g. School, Community, Individual, Peers, Family) > > > > Issues > > IssuesID <PK> > > Issues (text, e.g. lack of role models) > > CategoryID <FK> > > > > StudentIssues > > CaseNoID <link to Cases Table> > > IssuesID <Link to issues Table> > > > > Actions > > ActionsID <PK> > > Actions (text, eg. New Adult Role Models) > > CategoryID <FK> > > > > StudentActions > > CaseNoID <link to Cases Table> > > ActionsID <link to Actions Table> > > > > Does this look right to anyone? > > > > Is it possible to merge the Actions and Issues tables together or is it best > > to leave them separate? > > > > Thank you in advance for your help > >
From: Jeff Boyce on 5 Apr 2010 19:28 While I'm sure that most (?all) students have a "homeroom teacher" at some point in time, it is true that they have the SAME homeroom teacher for all time? Barring court or marital action, most individuals have/keep the same first and last name throughout their lives. I suspect your [HomeroomTeacher] field (and possible some of your {other info relating to the student} actually belongs in a different table). Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "forest8" <forest8(a)discussions.microsoft.com> wrote in message news:2840719A-1D88-4472-A69D-F253F6FF5D35(a)microsoft.com... > Hi > > This is a follow to a previous question concerning relationships in a > table. > > These are my tables I have in my database. > > Students > StudentsID > LastName > FirstName > HomeroomTeacher > (ohter info relating to the student) > > Cases > CaseNo_ID <PK> > StudentID <FK> > > Categories > CategoryID <PK> > Category (e.g. School, Community, Individual, Peers, Family) > > Issues > IssuesID <PK> > Issues (text, e.g. lack of role models) > CategoryID <FK> > > StudentIssues > CaseNoID <link to Cases Table> > IssuesID <Link to issues Table> > > Actions > ActionsID <PK> > Actions (text, eg. New Adult Role Models) > CategoryID <FK> > > StudentActions > CaseNoID <link to Cases Table> > ActionsID <link to Actions Table> > > Does this look right to anyone? > > Is it possible to merge the Actions and Issues tables together or is it > best > to leave them separate? > > Thank you in advance for your help >
From: Steve on 5 Apr 2010 20:00
<<Does this look right to anyone?>> No! You need a teachers table: TblTeacher TeacherID <other teacher fields> You need a classroom table: TblClassroom ClassroomID Classroom You need a homeroom teacher table. You will need to record this every school year. TblHomeroomTeacher HomeroomTeacherID ClassroomID TeacherID SchoolYear You can now record a student's homeroom teacher which identifies the school year and identifies the student's homeroom. You will need to record this every school year. TblStudent StudentsID LastName FirstName (ohter info relating to the student) TblStudentHomeroom StudentHomeroomID StudentID HomeroomTeacherID Regarding issues and actions ........ First, your category table looks good: TblCategory CategoryID <PK> Category (e.g. School, Community, Individual, Peers, Family) Your Issue table looks good: TblIssue IssueID <PK> CategoryID <FK> Issue (text, e.g. lack of role models) Your action table looks good: TblAction ActionsID <PK> CategoryID <FK> Action (text, eg. New Adult Role Models) Now you need a table that identifies the appropriate actions for each issue: TblIssueAction IssueActionID IssueID ActionID Now for Cases. I am going to assume you want to create a case history for a student each school year. This means at the first time there is an issue with a student in a school year, he is assigned a case number and keeps that same case number throughout the school year. In the next school year, if there is an issue with a student, he is assigned a new case number. TblCase CaseID StudentHomeroomID (identifies the student, his home room and the school year) CaseNumber Now you need a table to record each time there is an issue in a case: TblCaseIssue CaseIssueID CaseID IssueID IssueDate Finally you need a table to record what actions were taken for each issue: TblCaseIssueAction CaseIssueActionID CaseIssueID ActionID ActionDate Steve santus(a)penn.com "forest8" <forest8(a)discussions.microsoft.com> wrote in message news:2840719A-1D88-4472-A69D-F253F6FF5D35(a)microsoft.com... > Hi > > This is a follow to a previous question concerning relationships in a > table. > > These are my tables I have in my database. > > Students > StudentsID > LastName > FirstName > HomeroomTeacher > (ohter info relating to the student) > > Cases > CaseNo_ID <PK> > StudentID <FK> > > Categories > CategoryID <PK> > Category (e.g. School, Community, Individual, Peers, Family) > > Issues > IssuesID <PK> > Issues (text, e.g. lack of role models) > CategoryID <FK> > > StudentIssues > CaseNoID <link to Cases Table> > IssuesID <Link to issues Table> > > Actions > ActionsID <PK> > Actions (text, eg. New Adult Role Models) > CategoryID <FK> > > StudentActions > CaseNoID <link to Cases Table> > ActionsID <link to Actions Table> > > Does this look right to anyone? > > Is it possible to merge the Actions and Issues tables together or is it > best > to leave them separate? > > Thank you in advance for your help > |