I can't reproduce this problem in OS X 10.4.8. I created a simple project that parses a date or tells you that parsedate failed. When I run it with my International settings set to "United States" customized to the European short date format, it works as expected. "31/07/2006" reports "Monday, July 31, 2006", wheareas "07/31/2006" results in "Parse failed".
On 12/29/06, Bart Pietercil <[EMAIL PROTECTED]> wrote:
Can I invite the members of the list to add themselves to the watch- list of this report http://www.realsoftware.com/feedback/viewreport.php?reportid=rvnirehl It states that the ParseDate function errors out on OSX when the international settings of the system are mixed, ie. Primary language "English", regional settings (including date) "Belgium". This seems to indicate that the function does NOT look at the date settings , contrary to what is stated in the LR. When the system is set this way and you feed parsedate a European date format as "31/07/2006" the function returns false. Feed it "07/31/2006" and the function returns True (and a Date) Change the system to Dutch (Belgian) and the parsedate will return true for "31/07/2006". So the moment the language is aligned with the regional settings the function works as expected. This is (to me at least) a very nasty bug, since the majority of my clients work with this international setting (3 official languages in Belgium, so a company easily standardises on English but is keeping the regional date setting)
_______________________________________________ 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>
