[AccessD] Entering an ISO date with input mask and full validation

[Jurgen Welz]

In French, they say 99 as quatre vingt dix neuf, or four twenty ten nine.  In English, one says 987,654,321 as nine hundred eighty seven million, six hundred fifty four thousand, three hundred twenty one.  How much sense would it make to say the niddle block first, the last and then the first?  That's the Sql standard.
Better yet, do the same with each block of three digits. You'd have to say fifty four and six hundred thousand, twenty one and three hundred, eighty seven and nine hundred million. There's your Sql standard.

The reason you say month - day in speech is that the year is implicitly the current year in common usage and that has become habit applied to historical and future dates. You can see the same issue with addresses. If i give out an address to a personal acquaintance, the address implies galaxy, planet, country, state/province, city.  What i give as an address is progressively more specific after the implicit portions.

In terns of sorting data, it only makes sense to begin with the largest or grossest division to be considered in a data set. The only reasonable order for dates is year, month, day, hour, minute....

Look up how many countries in the world don't primarily use the metric system and perhaps question why US Microsoft standardizes on yyyy-mm-dd.   Oh, I think I understand your comment.

Jurgen Welz
________________________________________
From: AccessD <accessd-bounces at databaseadvisors.com> on behalf of Susan Harkins <ssharkins at gmail.com>
Sent: January 14, 2016 7:44:33 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Entering an ISO date with input mask and full    validation

But how do we speak these days? In the US, we "say" January fifth, 2016. We don't say, 2016, January 5 or the fifth day of January 2016. So, why would we write it any differently? Does any culture speak the year first?

Why is the year first more easily understood? Only because someone likes it that way -- there's no inherent property that makes it this way.

Susan H.

Actually, what doesn't make sense is the mm-dd-yyyy layout. When you see
01-05-2016 you can't be sure if it's 5th Jan or 1st May that the rest of the world would assume.

yyyy-mm-dd will be understood the world over and I, for one, would like it universally adopted.  Even countries that do not normally use the calendar based on some event around 2000 years ago will still understand.

---


Peter

On 2016-01-14 14:13, Dan Waters wrote:
> Hi Gustav,
>
> This format doesn't make sense, but is the reverse of what is
> typically used in the US (mm-dd-yyyy).  I'm going to guess that
> someone had a momentary bout of dyslexia and just read it backwards.
>
> I like using yyyy-mm-dd whenever I can just because it sorts correctly.
>
> Dan
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
> Of Gustav Brock
> Sent: Thursday, January 14, 2016 3:31 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Entering an ISO date with input mask and full
> validation
>
> Hi all
>
> I received a reader comment on this, claiming that "the US uses
> yyyy-dd-mm format".
>
> This is new to me. I have never seen anything else than mm/dd/yyyy for
> date formats related to the US.
> Can anyone confirm the use of the yyyy-dd-mm format?
>
> /gustav
>
>
> -----Oprindelig meddelelse-----
> Fra: AccessD [mailto:accessd-bounces at databaseadvisors.com] På vegne af
> Gustav Brock
> Sendt: 1. januar 2016 19:47
> Til: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Emne: Re: [AccessD] Entering an ISO date with input mask and full
> validation
>
> Happy New Year to all.
>
> I've made a "sister" demo of the time entry textbox - now for a date
> entry in the ISO yyyy-mm-dd format.
>
> Again, a demo is included, ready to download and run:
>
>     http://rdsrc.us/5xabOS
>
> The error catching is somewhat different, but the inputmask plays a
> big role.
>
> /gustav
>
> ________________________________________
> Fra: AccessD <accessd-bounces at databaseadvisors.com> på vegne af Gustav
> Brock <gustav at cactus.dk>
> Sendt: 11. december 2015 14:07
> Til: Access Developers discussion and problem solving
> Emne: [AccessD] Entering 24-hour time with input mask and full
> validation
>
> Hi all
>
> Years ago - in Access 2.0 - I made a form with a bound textbox for
> 24-hour fool-proof input.
> Recently, I had this need again, so I brushed it up for A2013/2016 and
> wrote down the thoughts behind as a note on Experts-Exchange.
>
> Here it is, including a demo ready to run:
>
>     http://rdsrc.us/Le82yJ
>
> It makes heavy use of an inputmask, the textbox's KeyPress event, and
> the form's Error event.
>
> /gustav
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com