Maybe I'm misinterpreting your scenario, here, but two points seem appropriate:
First off, this design is most unusual! Why do you have November's data in the three-month Table and in a separate Table? Assuming that both Tables have identical Fields, the three-month Table should suffice.
Secondly, does your Record have a Field defined as a DateTime Datatype, as opposed to, say, a Text Field that has 'November' as a Value for the Records of that month? If so, the Criteria for that Field, to exclude November, would be
The Access Gnomes will take that Criteria and create a WHERE Clause in the underlying SQL Statement that will read
If you Save your Query, Close it, and re-open it, you will find that they've actually created a Calculated Field with the name as DatePart("m",[YourDateField]) and its Criteria as <> 11, with the Field set to not display when the Query is Run.
Also, is this a one-shot deal, or will you be repeating this, down the road, excluding a different month? If so, you'd probably need to add a Parameter to the Query.
BTW, you'd only use Like (or Not Like, in this case) if you had a Field whose Value would be the month's name, and some people were entering "November," while others were simply entering "Nov."
Last edited by Missinglinq; 12-13-12 at 14:16.
Hope this helps!
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007