Re: An array within a table--Break into 1-to-1 mini tables or separate rows?
- From: "Duane Hookom" <DuaneAtNoSpanHookomDotNet>
- Date: Mon, 13 Nov 2006 00:12:42 -0600
Normalize, Normalize, Normalize,.. ;-)
Whether you store Null values depends on your business rules.
--
Duane Hookom
MS Access MVP
"Todd" <cashlord@xxxxxxxxxxx> wrote in message
news:ulzMBstBHHA.4428@xxxxxxxxxxxxxxxxxxxxxxx
I have a table that needs to hold the monthly grade of our members
locations. There are 6 aspects to this grade. Now, each inspection will
always give a grade for each of the 6 aspects. Do I keep the 6 columns in
the main table? Or, do I create a child table with each row holding the
grade for each aspect?
AND, if the grade is zero, do I not add the row for that aspect? IE: when
I get a null row while looking for the row for that aspect, do I count the
value as zero?
Should I just keep all 6 aspects within the main table?
Also, there are 4 other groups of grades like this. So, in reality there
are 40 columns like this!!
The un-normalized table:
ID PK
Name Varchar
Age Int
Grade_CommunicationRating Int
Grade_Cleanliness Int
Grade_TaxCompliance Int
Grade_Staffing Int
Grade_Insurance Int
Grade_Stocking Int
Grade_OVERALL Int
Normalized:
MAIN TABLE:
ID PK
Name Varchar
Age Int
GRADES TABLE:
ID PK/FK
GradeType PK
Rating Int
Thanks for your help!
.
- References:
- Prev by Date: An array within a table--Break into 1-to-1 mini tables or separate rows?
- Next by Date: Re: Attribute-value approach for table design
- Previous by thread: An array within a table--Break into 1-to-1 mini tables or separate rows?
- Next by thread: Re: An array within a table--Break into 1-to-1 mini tables or separate rows?
- Index(es):
Relevant Pages
|
