But that dosent explain why the same criteria "Month(Now())" works for me in
different DB on a different computer.
As described - IT DOESN'T work on your other computer.
I suspect that the criterion on the other computer is being applied, not to a
Date/Time field, but to a calculated field such as Month([datefield]).
Here's a plain, unvarnished fact: the function Month(Now()) will return an
integer number 1 for me for the next hour or so. Then it will be February, and
the function will return an integer number 2. This is not a library error,
this is not a mistake, this is not a bug - this is precisely what the Month()
function is documented to do, and precisely what it is doing on your computer.
Try it. Type Ctrl-G to open the VBA editor window, and type
?Month(Now())
in the Immediate window. See what you get. Try it on the other database. See
what you get there.
John W. Vinson [MVP]