Le 5 sept. 2009 à 22:59:19, LuKreme a écrit :
set myTest to "31/12/1943 Arpajon (Seine et Oise)" as string
set myDate to date (myTest)
return myDate
—> date "Friday, 31 December 1943 00:00:00"
set myTest to "samedi 5 septembre 2009 17:12:20" as string
set myDate to date (myTest)
return myDate
—> error "Invalid date and time date samedi 5 septembre 2009 17:12:20 of «script»." number −30720
Thanks.
set mytest to "12/31/1943"
set myDate to date (mytest)
returns
error "Date et heure invalides date 12/31/1943 of «script»." number -30720
We already know that the date behaviour may change with the AM/PM setting.
But, my question clearly asked upon a precise setting.
I have no reason to guess that luKreme responded about an other setting than the one asked about.
Given its response, it seems clear that systems set to mm/dd/yyyy date format are able to decipher the dd/mm/yyyy format too.
Or luKreme response was odd but I have no reason to think that !
Of course, if luKreme's response was odd,
we get an annoying but consistent behavior and my remark upon apartheid/segregation is wrong too
but Mark J. Reed was not 'firing' me upon the date's behavior but upon the used word.
At this time, I have
one user (luKreme) writing that it's system set to mm/dd/yyyy is able to decipher dd/mm/yyyy
and
one user (Michelle Steiner) writing that it's system set to mm/dd/yyyy is unable to decipher dd/mm/yyyy
At least, it's a bit surprising !
Yvan KOENIG (VALLAURIS, France) dimanche 6 septembre 2009 16:44:31