R
redsanders
As central office personnel visit our schools, they are to log details of
each visit. For example, during a visit, one may observe just the Special
Ed. features of a class. Or, during that SAME visit, s/he may also observe
how science, math or social studies is being taught to the Sp. Ed. students
in that class. Additionally, during that SAME visit s/he may observe small
group and large group instruction, and is to take note of such. Furthermore,
the visitor is to use narratives to enter: 1. The Objective being taught; 2.
A summary of activities observed (including comments about those activities)
and; 3. Recommendations. Members from other departments (math, technology,
bilingual, etc.) would have similar experiences.
I've created tbl_Visitors which contains five fields: Employee_Num
(Primary), Last, First, Department and Position. (The last two are lookups
from tbl_dept and tbl_position.). This table is linked to a tbl_visits, with
a one to many relationship, with the Employee_Num being the foreign key in
the tbl_visits.
But, here's where get worred. As currently designed, each record in the
tbl_visits has 22 check box fields (so as to indicate content area(s) and
methods(s) of instruction observed, as described above). Furthermore, each
record has three memo fields for the three narratives described above. Once
launced, I fully expect requests to for the inclusion of even more features
observed during a visit!!
From all that I read, I'm asking for trouble. I have too many fields in the
table, and am risking corruption by using memo fields, especially three per
record. Plans are for almost 60 people to use this database. I am prepared
to create a back end for tables on a shared drive. and a front en on each
user's computer for the remaining components of the database. But, if I have
poorly normalized tables, I expect this thing to crash and burn & I'll have
to leave town! I just don't comprehend normailzation sufficiently to apply
its principals here. ANY help in redesign would be MOST appreciated.
each visit. For example, during a visit, one may observe just the Special
Ed. features of a class. Or, during that SAME visit, s/he may also observe
how science, math or social studies is being taught to the Sp. Ed. students
in that class. Additionally, during that SAME visit s/he may observe small
group and large group instruction, and is to take note of such. Furthermore,
the visitor is to use narratives to enter: 1. The Objective being taught; 2.
A summary of activities observed (including comments about those activities)
and; 3. Recommendations. Members from other departments (math, technology,
bilingual, etc.) would have similar experiences.
I've created tbl_Visitors which contains five fields: Employee_Num
(Primary), Last, First, Department and Position. (The last two are lookups
from tbl_dept and tbl_position.). This table is linked to a tbl_visits, with
a one to many relationship, with the Employee_Num being the foreign key in
the tbl_visits.
But, here's where get worred. As currently designed, each record in the
tbl_visits has 22 check box fields (so as to indicate content area(s) and
methods(s) of instruction observed, as described above). Furthermore, each
record has three memo fields for the three narratives described above. Once
launced, I fully expect requests to for the inclusion of even more features
observed during a visit!!
From all that I read, I'm asking for trouble. I have too many fields in the
table, and am risking corruption by using memo fields, especially three per
record. Plans are for almost 60 people to use this database. I am prepared
to create a back end for tables on a shared drive. and a front en on each
user's computer for the remaining components of the database. But, if I have
poorly normalized tables, I expect this thing to crash and burn & I'll have
to leave town! I just don't comprehend normailzation sufficiently to apply
its principals here. ANY help in redesign would be MOST appreciated.