If I understand you correctly (note that bold thar), you have one of two choices. Both involve running a make-table query which will generate table3.
Either
- You have some sort of unique key, or set of keys, common to table1 and table2, in which case you build the query by adding table1 and table2 to the "add tables" bit, create a join from each table1.KeyField to each table2.KeyField, and double-click each join, make it an "outer join", option number 2, all records from table1 and only those records from table2 that match, then set your criteria to where one of the table2.KeyField s "Is Null".
- or you just run it against table1, and reverse the criteria you used to pull out the table2 records. Something like DteLogged < DateAdd("yyyy",-2,dateyoumade table2) and then a second group-by query counting each instance, only pull those <5 or <=5.
Sloppier, and may not get all 60000, but should get pretty close.
I'm not sure how much of this reply you can understand. You'll let us know, though, and we'll help you out from there.
(Dreamy's right, by the way, in a sense. If table2 replaces table1, you should've deleted the table2 records from table1 when you made table2. Then you wouldn't need a table3.)