The Date field works the same as the Date/Time field from the database side. They both record time in seconds. The difference is from the User side. Date does not give you time of day selection, but it will set to 00:00:00 for the day choosen. So your query would have to be:
('Effective Date' >= $DATE$ - (60*60*24))
OR
('Effective Date' >= $DATE$ - 86400)
.ron
On 9/26/06, Aaron Keller <[EMAIL PROTECTED]> wrote:
**__20060125_______________________This posting was submitted with HTML in it___I've got a DATE field (not a Date/Time field) from which I want to query relative to the current day.
This works:
('Effective Date' >= $DATE$)
But this does not:
('Effective Date' >= $DATE$ - 1)
But strangely enough, this DOES work:
('Effective Date' >= $DATE$ - 1156789196)
So it looks like the $DATE$ keyword evaluates in the date format (days) when used by itself with a date field, but evaluates in the date/time format (seconds) when used in arithmetic. The problem is that each day will add another 864399 to what needs to be subtracted, which makes things much more complicated for an escalation!
Is there some way to work with date fields in queries that I'm missing?
-Aaron
* Email: [EMAIL PROTECTED]
SunCom is the wireless company that's committed to doing things differently.
Things we want you to know.
This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication may contain material protected by the attorney-client privilege. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited.
__20060125_______________________This posting was submitted with HTML in it___
