**
From
the Dev Guide: Date fields A date field stores date information only, as the number of days
from the beginning of its range. Use a Date field when you want to compare
two dates or perform calculations based on the date, such as calculating the
number of days between two dates. Users can enter dates from January 1, 4713
B.C. to January 1, 9999 A.D. in the Date field. -A From: Action Request
System discussion list(ARSList) [mailto: ** Not sure about that
statement "They both record time in seconds". I believe a DATE only
field stores time in days since BC - not sure of the exact date On 9/26/06, Ron
Tavares <[EMAIL PROTECTED]>
wrote: ** 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:
OR ('Effective Date' >= $DATE$ - 86400) .ron
On 9/26/06, ** 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]
__20060125_______________________This posting was submitted with HTML
in it___
|
- Re: DATE fields and queries Ron Tavares
- Re: DATE fields and queries Frank Caruso
- Re: DATE fields and queries Aaron Keller
- Re: DATE fields and queries Aaron Keller