Our administration wishes (as I said, for funding
purposes) to keep track of how many of our students are
under the age of 21. The student's birthdate is included
in the student record information sent from the board
office. My boss wants to include a boolean field in our
student table that, by way of a checkbox, will indicate at
a glance weather or not the student fits the under 21 bill.
Your boss should either learn some basic principles of relational
databases, or be willing to listen to you as the expert. S/he is
wrong.
The existance of such a field in the table IS BAD DESIGN and IS NOT
NECESSARY. Also, it presumes that the boss will be looking at the
table datasheet directly - bosses should never be allowed to do so
<bg>.
The data seen by the boss, or any other *user* of the data, should be
displayed upon a Form or a Report (for printing). This Form or Report
can be based on a Query with a calculated field:
Under21: [DOB] < DateAdd("yyyy", -21, Date())
This calculated yes/no value can be displayed in a checkbox control on
the Form or Report, and will accurately reflect the student's age
anytime. If the yes/no field is stored in the Table, you'll need to
run an update query EVERY SINGLE DAY in order to ensure that you don't
miss someone's 21st birthday.