[AccessD] Date standardization

Hi Gustav:

That is true but all the entry points that I could find in the original FE
MDB, I set to 'dd Mon yyyy'. My fear is that the client has decided for
expedience sake that direct entry into the tables was faster. 8-(

Jim


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Wednesday, June 16, 2010 6:41 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Date standardization

Hi Doug

But that is not because of the regional settings but because validation is
missing and/or if the user types the date in a way not according to the
regional settings. 11/6/10 (November) can be perfectly valid (think of a
booking system), but if future dates are not allowed, the app must validate
input and prompt the user.

/gustav


>>> dbdoug at gmail.com 16-06-2010 15:24 >>>
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