Phillip

Consider, before you pursue this any further, revisiting your data
structure.  If you have identical tables to store data from different
(months, counties, clubs, ... fill in the blank), you are likely "committing
spreadsheet" on Access, a relational database.

Your task is made harder by the fact that you have to visit/refer to
multiple tables, and you will have to modify how you refer to those tables
every time you add/remove another (month, county, club, ... you get the
idea, right?).

On the other hand, if you had ONE table, with a single additional field for
"county" (in your situation), you could query against that ONE table for ALL
records matching a set of selection criteria.  For example, you could use a
DateCreated field to find all records added since that date.

Which brings up another opportunity for normalizing your data structure.
Any time you have a one-to-many relationship, you can create a "child" table
to hold the "many" records, rather than, as it sounds like from your
description, adding more columns ("... multiple document types and multiple
dates of record entry for each client."

I suspect you would find your task much easier if your data structure was
better normalized.