On Dec 14, 2006, at 8:32 PM, Karen wrote:
On Dec 14, 2006, at 8:27 PM, Michael wrote:
The workaround is quite simple...once one knows what it is.
Once d is acquired with parsedate, setting d.hours/d.min/d.seconds
to 0 solved it for me.
I know it is simple ... that was not the point.
It should not NEED to be worked around and as things are could
introduce subtle bugs that could easily not be caught in testing if
you don't know about it.
Perhaps you guys should file a feature request for ParseDate to
return a Date object with time 00:00:00 when it returns one.
Predictability is nice, most of the time.
Charles Yeomans
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
