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.
michael.
On Dec 14, 2006, at 4:24 PM, Karen wrote:
On Dec 13, 2006, at 5:48 PM, Michael wrote:
If the date is NOT the current date, works on both platforms,
(returns a date object at midnight) but if the date is the current
date, parsedate returns
=midnight on the Mac
= the current time on Windows.
Is this known ?
This was noticed as a bug and supposedly fixed in 2002...
Apparently the bug crept back in...
http://www.realsoftware.com/feedback/viewreport.php?reportid=uxsvwiwc
I asked for it to re-opened but as this time around, the response
on the forum was it was not a bug because it uses the windows OS
call, I'm not optimistic about it being re-opened and fixed...
Obviously I think when RS provides an API for something like
ParseDate it should where return the same value for equivalent
inputs (same date) on all platforms, else RB is not XPlatform
programming that just works...
Talk about potentially subtle bugs in this case! And in this case
even on a single platform (Windows)!
- karen
_______________________________________________
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>
_______________________________________________
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>
