This has been driving me crazy for a long time while working on the runtime solution I plan to market later this year: what would be the "best" date format to code it in for data input? I'd like to market it first in the U.S. and Canada, then worldwide.
Here's the thing...
Here in the U.S., we use the MM-DD-YYYY format; our friends to the north use both DD-MM-YYYY ( as in 03-MAR-2013) and ISO 8601's YYYY-MM-DD format; other nations have their own or similar formats. What I want to avoid is having to create different versions of the same runtime for use in different countries--that would be a headache to maintain.
Two problems right off the bat are that it's a runtime so users can't customize date input fields to whatever style they want. The second is that the date fields inherit the date format the "master" file is set at so, for example, if I set my Mac's and PC's preferred date format to MM-DD-YYYY, that's what gets encoded into the runtime (as far as I can tell) as the default date format.
What I've done so far is create a global date format field so users can print lists and reports in the date format of their choice (which they choose from an editable value list). However, when it comes to data input...? I suppose ideally I would set every date field to ISO 8601's standard since that is the standard everyone is suppose to follow/use, but I don't want to annoy my largest market share (Americans) with a date format they're unaccustomed to.
As always, your input/help is appreciated!