That would work, but for instance, i need a list of everyone 26 and under,
for defensive driving classes, and i need a separate list for everyone under
21 wouldnt i just be making more work for myself?
No. You'ld be making it EASIER for yourself.
You should not store the age in any table. Storing derived data such as this
in your table accomplishes three things: it wastes disk space; it wastes time
(almost any calculation will be MUCH faster than a disk fetch); and
most importantly, it risks data corruption. If one of the underlying fields is
subsequently edited, you will have data in your table WHICH IS WRONG, and no
automatic way to detect that fact. In fact, for an age, you can be absolutely
certain that every record in your table will have an incorrect age within a
year!
Just redo the calculation whenever you need it as a calculated field in a
Query; you can apply criteria such as >26, or >21, or > [Enter cutoff age:] to
get a prompt, or > [Forms]![YourForm]![txtCutoff] to pull the criterion from a
form. It is NOT necessary to store the data redundantly in your table.
If you're routinely working in table datasheets... don't. That's not their
purpose! Use Queries and Forms, the tools that Access provides for working
with the data in tables.