How hard could it be to allow tools like FastTrack, Metadata Workbench and so on to use local date formats rather than US ones?
Dates like 1/17/12 are anathema in my part of the world, where DMY is the default order.
If that's too hard, why not hard code every date in ISO 8601 format (CCYY-MM-DD HH:MM:SS)?
Local Date Formats
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Local Date Formats
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I agree. Same with numeric formats.
Why, for example, do I have to switch my German Windows-client to English-US regional settings to work with Quality-Stage Match-Designer in order to avoid errors related to incorrect decimal-separators?
How hard could it be to transform that to the appropiate format needed by the server?
Why, for example, do I have to switch my German Windows-client to English-US regional settings to work with Quality-Stage Match-Designer in order to avoid errors related to incorrect decimal-separators?
How hard could it be to transform that to the appropiate format needed by the server?
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon
There are the grateful those are happy." Francis Bacon