Students [Table] can have many classes. StudentID would be auto-enter, Serial Number
Classes [Table] can have many Students. ClassID would be auto-enter, Serial Number.
Attendance [Table] would link Students to Classes and would contain StudentID (entered) and ClassID (entered)About planning a databaseA well-designed database promotes consistent data entry and retrieval, and reduces the existence of duplicate data among the database tables. Relational database tables work together to ensure that the correct data is available when you need it. It’s a good idea to plan a database on paper first.Follow these general steps to plan a database:
Relational Database Design 101 (part 1 of 3): Designing a Flat File Database
Relational Database Design 101 (part 2 of 3)
Relational Database Design 101 (part 3 of 3)
I think you should add the belt as a lookup field in the attendance table.
That way that value gets "copied" from the student table and stored in the attendance table every time you enter an attendance.
Then afterwards you could create a sub summary report that counts the amount of attendanced per student and per belt type.
If you want a beginners tutorial screencast you could watch this video:
So your attendance table should have the fields:
ID a number field with auto enter serial number
Date - A date field for the date of attendance
StudentIdFk - Where you store the ID of the student
BeltLookup - That looks up the belt the student has at that moment.
CountId - A summary field that counts the ID field. So you can always know how many times a student attended.