Error with SetLocale and LSDateFormat

Question

Why does the following code below throw an invalid date error
in the final line.
If I change the first to setLocale("ENGLISH (CANADIAN)") it
works fine
Also ENGLISH(UK) works fine but ENGLISH(NEW ZEALAND) throws
an error
I'm on 7.0.2 Windows

Answer 1

BKBK wrote:
> Yes, you may. The function createDatetime() is
universal, that is,
> locale-independent.
it's a localized datetime STRING.
> The trouble with this logic is that you presume
"11/4/2007 12:32:00 PM", for
i'm not presuming anything, that's what it is & that's
the intent from the
original poster.
> may well fail in a locale. Whereas, the related
universal function,
i said *valid* localized datetime string. if its not valid
for a given locale,
the parsing process will tell you. if you start w/a localized
datetime string,
there's no way on earth you can use createDateTime(), etc. to
get a back a
datetime object for all possible locales. that's why, cf,
java, etc have
datetime string parsing methods.
> correct locale datetime is another matter. My point is
simply that there could
> be problems when a string is interpreted as a date-time
object.
it's a localized datetime string. you need to parse it. you
can't use
createDateTime, etc. methods on a localized datetime string.
period.
> I wasn't suggesting you should or could. Just sounding a
warning that passing
> "a localized datetime string" as a date-time object can
be problematic.
everybody should know you have to parse localized datetime
strings. sometimes
you have to use what's given to you.
> Nothing you've said refutes my suggestion,
your suggestion is irrelevant to this issue.
> which works in
every locale.
not if you start w/a localized datetime string.