Don't understand the relationship between a combo box and a ta
Currently it's one field per issue.
"John W. Vinson" wrote:
On Tue, 30 Mar 2010 19:32:01 -0700, forest8
wrote:
In previous posts, I was asking for assistance in creating a Case Management
Datatabase.
In this database, there are 5 categories of investigation:
School, Community, Individual, Peers, and Family.
In the School category, there can be anywhere from one to seven actions a
youth can take depending on how he has answered previous questions.
For instance, if the youth answered that he has no role models, then the
reaction is to help the youth obtain positive role models, positive support,
and/or Empowerment but not necessary all can/would be chosen.
All this information is hopefully placed in a form in which at each phase of
their involvement in the program, all their youth's responses can be reviewed.
If I split up my form into the categories by phase, this can mean an
additional 25 tables.
This would bring my total tables to almost 100.
I can't create any more relationships since I am at the limit.
How about:
Students
StudentID primary key
LastName
FirstName
other biographical info as appropriate
SchoolID where is this student enrolled
Cases
CaseNo primary key
StudentID link to Students, who is being investigated
other fields relevant to the case as a whole
Categories
CatgoryID primary key
Category (e.g. School, Community, ...)
Issues
IssueID primary key
Description text, e.g. "lack of role models"
CategoryID in which category is this issue
StudentIssues
CaseNo link to Cases and thence to Students
IssueID link to Issues, which issue did this student raise
Similar tables for Responses, not sure how you want them linked.
Note that NONE of these tables need more than two or three indexes.
How are your tables structured? One field per issue perhaps, or one field per
response? That may be the source of your problems!
--
John W. Vinson [MVP]
.
|