Jim Lawrence
accessd at shaw.ca
Wed Jun 16 15:41:46 CDT 2010
Thanks Doug: That is a good point to remember. Before I get a copy of the data I will do that check first. Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Steele Sent: Wednesday, June 16, 2010 6:25 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Date standardization I have had problems in BE databases when some of the client computers with the FE dbs have had different regional settings for dates. If you are getting obviously invalid dates like 11/6/10 for data that you know was entered in June, a client computer may have its Short Date format set as dd/mm/yy, not mm/dd/yy. Doug On Wed, Jun 16, 2010 at 12:34 AM, Gustav Brock <Gustav at cactus.dk> wrote: > Hi Jim > > This can only happen if dates are not stored as data type date/time but as > text, and this can cause all sorts of trouble as validation is not possible > at the table level. > If "wrong" dates are stored, say 12/5/2010 as 5/12/2010, only manual > correction is possible unless you in some other way can sort the records. > > /gustav > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com