Weird A97 Date Problem

[andybriggs]

An Access 97 database is running quite happily on about 30 IBM
ThinkPads. Some of the users, however, have now installed some
components of Office 2000 like Word and Excel. On those machines, the
A97 db now only stores dates in American date format, so that a British
date entered as 23/04/03, for example, is stored as 03/04/23. Existing
dates in the database are now displayed in American format too. I have
cured the problem by re-installing A97 on those machines, but does
anybody know a) why this problem occurs, and b) if there is a fix that
doesn't involve a re-install? Many thanks.

Andy Briggs

Elmhurst Solutions Limited

http://www.elmhurstsolutions.com
--
Andy Briggs
Elmhurst Solutions Limited
http://www.elmhurstsolutions.com
Posted via http://dbforums.com

[andybriggs]

Many thanks Doug - you're right, the data isn't being stored in American
date format, but in the format yy/mm/dd. Short date format on the
affected machines is universally dd/mm/yy. As I say, this change only
happened after components of Office 2000 were installed, so I'm guessing
it's something to do with a shared DLL. I've tried converting the data
back to dd/mm/yy before outputting it into reports (which is where the
problem is causing much confusion) but the affected machines will not
recognise something like 23/04/03 as a valid date, even if I split the
day/month/year components apart and concatenate them into the right
order. Any further ideas much appreciated.
--
Andy Briggs
Elmhurst Solutions Limited
http://www.elmhurstsolutions.com
Posted via http://dbforums.com

[Douglas J. Steele]

Reread my post. Dates are NOT stored with a format: they're stored as
numbers only.

Did you read Allen's essay as I suggested?

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
"andybriggs" <me*********@dbforums.com> wrote in message
news:33****************@dbforums.com...

Many thanks Doug - you're right, the data isn't being stored in American
date format, but in the format yy/mm/dd. Short date format on the
affected machines is universally dd/mm/yy. As I say, this change only
happened after components of Office 2000 were installed, so I'm guessing
it's something to do with a shared DLL. I've tried converting the data
back to dd/mm/yy before outputting it into reports (which is where the
problem is causing much confusion) but the affected machines will not
recognise something like 23/04/03 as a valid date, even if I split the
day/month/year components apart and concatenate them into the right
order. Any further ideas much appreciated.
--
Andy Briggs
Elmhurst Solutions Limited
http://www.elmhurstsolutions.com
Posted via http://dbforums.com