in the mean time, you could simply override ParseDate() with a
function of your own, which performs RB's flawed internal function
and then replaces the leading 0 with a 2.
You should be able to simply delete your overridden function once
REAL fix this, as long as they do that within the next 993 years of
course.
- Tom
On 04/01/2007, at 8:28 PM, Michael Maclean wrote:
ParseDate(s, d) seems to be broken in RB2007r1.
s = "4 Jan 07"
ok = ParseDate(s, d)
then d.SQLDate produces "0007-01-04" instead of "2007-01-04".
I shall have to stop using 2007r1 since I use ParseDate() quite a lot.
The bug report is qbrbthfn.
Michael Maclean
[EMAIL PROTECTED]
_______________________________________________
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>
