Yes, both the combo0 and date field in the table have date and time.
The table is formatted in a short date, but the input mask is 99/99/0000;0;
And the combo0 is imported on a macro to a caption. the expression is Now()
The table is formatted in a short date
Not really. Dates are carried as floating point decimal fields and have no
internal formatting, Any formatting is done when the data are retrieved, not
when it is stored.
Input Masks only control how the user is allowed to enter values, not how
the values are stored for dates. For text fields, you have that option;
however.
Formats only control how the value is to be displayed when retrieved.
Again, it has no effect on how the value is stored.
the input mask is 99/99/0000;0;
This means the user can only put in month, day, and year. There is no
facility to enter time.
the combo0 is imported on a macro to a caption
This part I don't understand.
But since you have times in the fields, you need to allow for that when you
are filtering. That is because when you do the comparisons, it considers the
entire value so that if you say <=#5/20/2008# That implies 05:20:2008
00:00:00 AM
If the value in the field is 05:20:2008 00:00:01 AM it will be excluded,
because it is greater than the compare value. For this reason, you should
only use time value in a date field when the time is important; otherwise, to
compare by date only, you need to exclude the time value. You can do that
using the DateValue() function. It returns only the date part.
So to get what you want, assuming your combo is 5/19/2008 and you want the
data form 5/12/2008 through 5/18/2008
BETWEEN DateValue(DateAdd("ww",-1,[Forms]![Print Weekly Reports]![Combo0]))
AND DateValue(DateAdd("d",-1,[Forms]![Print Weekly Reports]![Combo0]))

Signature
Dave Hargis, Microsoft Access MVP
> Yes, both the combo0 and date field in the table have date and time.
> The table is formatted in a short date, but the input mask is 99/99/0000;0;
[quoted text clipped - 46 lines]
> > > > > > >
> > > > > > > Thanks in advance.
lovespar - 20 May 2008 20:35 GMT
We are almos there! I am picking up the 12th (M0nday now but I am not picking
up the 18th(Sunday). I see where the "d" is the day but what is the "ww"?
> The table is formatted in a short date
> Not really. Dates are carried as floating point decimal fields and have no
[quoted text clipped - 81 lines]
> > > > > > > >
> > > > > > > > Thanks in advance.
lovespar - 20 May 2008 21:34 GMT
Thanks again,
I have it now. I replaced the -1 with a 0 and pulled all the dates I needed.
WW stands for week of the year so now it is all falling into place.
> The table is formatted in a short date
> Not really. Dates are carried as floating point decimal fields and have no
[quoted text clipped - 81 lines]
> > > > > > > >
> > > > > > > > Thanks in advance.
Klatuu - 20 May 2008 21:56 GMT
Actually, the arguement tells the function what interval of time to add.
d = day
w = weekday (1 = sunday, 2 = monday, etc)
ww = week
m = month
etc.
I don't know why -1 doesn't work because it should return 5/18/2008. 0
would not add or subtract anything.

Signature
Dave Hargis, Microsoft Access MVP
> Thanks again,
> I have it now. I replaced the -1 with a 0 and pulled all the dates I needed.
[quoted text clipped - 85 lines]
> > > > > > > > >
> > > > > > > > > Thanks in advance.