//
If you don't reference the year in a date field it assumes the current year,
so #11/15# will be 11/15/2010 if you run the query today, 11/15/2011 if you
run it next year.
//

I inferred as much from your original post.


//
My suggestion WILL WORK, if you try it. It will work this year, it will work
next year, it will work in any year.
//

If you refer to my StartDate as the object of your "not referencing", how?
It is a reservation that must be day/month/year specific.

So, if you do not mean that--why do I not return a StartDate of 1/05/11,
when I do return a date of 11/20/10?

Again, please not that my criteria for [StartDate] is

"Date() And (DateSerial(Year([StartDate]),4,1) Or
DateSerial(Year([StartDate]),11,15)) "


I follow the logic, it makes sense, but does not return as advertised.

What could be the issue?

--
Chrissy


"John W. Vinson" wrote:

On Wed, 12 May 2010 14:46:06 -0700, Chrissy
wrote:

Thanks, John.

I test on the StartDate, future only. So I entered...

Date() And (DateSerial(Year([StartDate]),4,1) Or DateSerial(Year([StartDate]),11,15))

This resulted, like what I was using, current year only.

What do I do about all future dates falling in this range in any future
year?

Thanks,

If you don't reference the year in a date field it assumes the current year,
so #11/15# will be 11/15/2010 if you run the query today, 11/15/2011 if you
run it next year.

My suggestion WILL WORK, if you try it. It will work this year, it will work
next year, it will work in any year.

--

John W. Vinson [MVP]
.