tables to be filled over the next six years

[oscar]

Greetings,

I am creating an access project for a teacher friend of mine who needs a
database to track his students assessment scores for the next six years.
What would be the best way to keep this info; one table for all six
years or one table per year? I am also concerned with how the form or
forms would populate the table or tables. Are there any existing templates?

Thank You,
Oscar

 

[Allen Browne]

Definitely one table, with a field to distinguish the year.

Typically you need these tables:
- Student one record for each student
- Subject one record for each unit.
- Class an instance of a Subject taught in a year.
- Enrol the Students in a Class.
- Assign the assignments for a Class
- Result the instances of students submitting assignments.

This structure copes with the fact that one Subject is taught many times
(many Classes over the years). Each class has many assignments with
different due dates. Since the assignments are tied to the Class (not the
Subject), it allows the teacher to set different assignments each time they
teach the class.

The Result table then contains a record for each time a student hands in an
assignment (for a class). You may need to allow the same assignment to be
submitted more than once by the same student (to cope with resubmissions).

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

I am creating an access project for a teacher friend of mine who needs a
database to track his students assessment scores for the next six years.
What would be the best way to keep this info; one table for all six
years or one table per year? I am also concerned with how the form or
forms would populate the table or tables. Are there any existing

templates?