Let me guess that [ID] is a unique student identifier (you didn't say),
and that it may therefore be used as the primary key of [Student] and
thus can be used elsewhere to identify a student.  (Incidentally, if I'm
correct about this, I suggest calling it something more descriptive,
like [Student_ID], that you can also use in other Tables when referring
to it.)

I suggest that you include at least two other Tables.  One could be a
list of dates that school is in session, perhaps to be called
[Calendar], but you might want a bit more detail and include such a list
for each class offered by the school, or even (but I think it's
unnecessary) a list of each student's individual appointments.

Assuming you just include a school calendar, the third Table, perhaps
called [Attendance], would link the two: each record could perhaps
contain a [Student_ID] foreign-key field linking to [Student], and a
[Present] field of Date/Time type that could be matched to a date in
[Calendar].  You could then easily list various statistics, such as a
list of dates that each student is absent (or on which he is present),
the number of days absent in a given time period, how many students were
absent at least once during each week, the average daily attendance
while school is in session, &c.  You could even present these in tabular
form (via a Crosstab Query), for example with a row for each student, a
column for each week, and the number of absences in each cell in the
body of the Datasheet.

If you have trouble doing any of this, it might help if you post both
your SQL and some example data, along with a description of the results
you want generated.

  -- Vincent Johns <vjohns@alumni.caltech.edu>
  Please feel free to quote anything I say here.