Short Date

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dave - 19 Nov 2004 17:53 GMT

I have an Access/SQL Server application that uses the short date format for
displaying dates. In Windows XP the default is M/d/yyyy which I change to
M/d/yy, the definition I need to use. I've noticed that with users that have
had Access 2003 installed on their computers that the short date settings in
the Regional settings control panel keep getting changed back to M/d/yyyy. I
don't know if this is Access 2003 or not but that seems to be the common
denominator. Does anyone know what is causing this to happen and how to
correct it?

Thanks for you help.

Signature

-Dave

Reply to this Message

Douglas J. Steele - 20 Nov 2004 14:55 GMT

Is it possible that your company is using policies to force everyone's date
setting? I know I'd certainly force people to use a 4 digit year.

Even if that's not the case, there's no way I'd use your application if it
forced me to change my personal settings, so I think it's necessary for you
to be able to handle other settings. If there's some legitimate reason to
only show a 2 digit year (and I'm unable to think of a good one), format the
field explicitly in your application rather than relying on the user
settings.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> I have an Access/SQL Server application that uses the short date format for
> displaying dates. In Windows XP the default is M/d/yyyy which I change to
[quoted text clipped - 6 lines]
>
> Thanks for you help.

Reply to this Message

Dave - 22 Nov 2004 15:00 GMT

Your not very imaginative if you can't think of a reason. The application was
written years before XP when short date was not a personal setting. There are
75 reports that get the ending dates chopped off because it now shows the
century instead of the year. No one in this company wants 4 digits years
because it is obvious what century the date refers to and it uses up valuable
real estate on reports that are tight on room. If anybody else has any ideas
rather than commentary, I would appreciate it.

> Is it possible that your company is using policies to force everyone's date
> setting? I know I'd certainly force people to use a 4 digit year.
[quoted text clipped - 20 lines]
> >
> > Thanks for you help.

Reply to this Message

Brendan Reynolds - 22 Nov 2004 16:27 GMT

Look for 'Name AutoCorrect'. However, before you get carried away, check out
Allen Browne's list of known issues with Name AutoCorrect at the following
URL ...

http://members.iinet.net.au/~allenbrowne/bug-03.html

Signature

Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

> Your not very imaginative if you can't think of a reason. The application
> was
[quoted text clipped - 40 lines]
>> >
>> > Thanks for you help.

Reply to this Message

Brendan Reynolds - 22 Nov 2004 16:37 GMT

Argh! How'd that get in here? Sorry, all, that was supposed to go to a
different thread.

Signature

> Look for 'Name AutoCorrect'. However, before you get carried away, check
> out Allen Browne's list of known issues with Name AutoCorrect at the
[quoted text clipped - 50 lines]
>>> >
>>> > Thanks for you help.

Reply to this Message

Douglas J. Steele - 22 Nov 2004 22:20 GMT

I take it, then, that the two different suggestions I made in addition to my
commentary didn't pan out?

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> Your not very imaginative if you can't think of a reason. The application was
> written years before XP when short date was not a personal setting. There are
[quoted text clipped - 28 lines]
> > >
> > > Thanks for you help.

Reply to this Message

Dave - 24 Nov 2004 15:41 GMT

One thing I've discovered in the meantime is that it isn't Access 2003, I'm
getting it with older versions as well. I will never use "shortdate" again
and I will need to redo a lot of legacy stuff. Thanks for your response.

-Dave

> I take it, then, that the two different suggestions I made in addition to my
> commentary didn't pan out?
[quoted text clipped - 47 lines]
> > > >
> > > > Thanks for you help.

Reply to this Message