David McAfee
davidmcafee at gmail.com
Fri Feb 17 12:27:32 CST 2012
Yes. I often name reports printed as PDF or exported as Excel in the format. It's so nice to have them sorted correctly in Windows Explorer. On Fri, Feb 17, 2012 at 10:22 AM, Mark A Matte <markamatte at hotmail.com>wrote: > > I move and receive a lot of date oriented data between/from SQL, MDB, XLS > ,CSV and TXT... > > I like yyyymmdd or even yyyy-mm-dd because I can sort it as text if > necessary and still get the desired result. > > Just my 2 cents... > > Mark M > > > > Date: Fri, 17 Feb 2012 19:22:39 +0100 > > From: Gustav at cactus.dk > > To: accessd at databaseadvisors.com > > Subject: Re: [AccessD] text control Date formats with SQL Server > > > > Hi Steve > > > > That is a nasty source of error because "mmm" is localized, thus this > will fail for most non-English locales. > > The ISO format is the only format which will never fail, that is why it > is the native format for most SQL engines including MySQL, SAP, and SQL > Server (since 2008 I think). > > > > /gustav > > > > > > >>> steve at goodhall.info 17-02-2012 18:44:58 >>> > > I disagree. I habitually use "dd-mmm-yy" or "dd-mmm-yyyy" (e,g, > "17-Feb-12") which are unambiguous for both US and international readers. > > > > Steve Goodhall, MSCS, PMP > > > > -----Original message----- > > From: David McAfee <davidmcafee at gmail.com> > > To: Access Developers discussion and problem solving < > accessd at databaseadvisors.com> > > Sent: Fri, Feb 17, 2012 17:39:15 GMT+00:00 > > Subject: Re: [AccessD] text control Date formats with SQL Server > > > > I wish the whole world would adopt that standard. YYYMMDD is the best > date > > display IMO. > > > > > > -- > > 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 >