You may be asking yourself why would you care? Why bother with
"normalization"?

MS Access is a relational database. It's features and functions are
optimized for well-normalized data. If you try to feed it 'sheet data, both
you and Access will have to work overtime to overcome that 'sheet data
structure.

Good luck!

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.


"J_Goddard via AccessMonster.com" u37558@uwe wrote in message
news:a4b7fe09ac16b@uwe...
If any one of the records in the table pertain to more than one subject,
then
it is not properly normalized (i.e. designed). If you have groups of
fields
that repeat, for example grade1, source1, approval1, grade2, source2,
approval2.... then it is not normalized at all.

Looking at your description (if I read it right, that all this is in one
table), then you do have that situation: for each student, in each
subject,
there are many scores. The scores in turn have fields for reviewer,
approval,
suggestions,.... Given this, "Scores" requires its own table, with a PK
of
Student_ID, Subject_ID, Score_ID, plus all the other data.

They may well be more tables that would result if you do the complete
normalization process, and the complexity might (and that's a big
*might*!)
not be as much as you think.

HTH

John




John Quinn wrote:
It is a sequence of information and approvals for each subject, grade,
homework and tests.

If a student is taking English then we need to show all scorces given and
the relationship to the previous grad or score. With each entry you must
always carrt fields of data for who reviewed it, approved it, made
suggestions or rejected the educational technique used. There is also a
comparison made to grades when the student goes into the next level of
education. For example from grade school to middles school, from middle
school to junior high and from junior high to college.

We even have to know that the student entered college and if that student
graduated or not.

The designers at Fort Hood, indicated iot was the toughest applications
they
have ever seen. Microsoft consultants were amazed at what the attorney's
in
Washington DC want us to keep an accounting of.

The bad data message comes from an append query. The tables are suppose
to
be identical but for some reason this happens once in a while. I
eventually
find out where the problem is, but it takes so long.

Thanks for the interest.

John Q.

Hi -

[quoted text clipped - 22 lines]

John Q

--
John Goddard
Ottawa, ON Canada
jrgoddard at cyberus dot ca

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/201003/1