No, it's not --- "It's not like this machine is actually running Access in a
Terminal Server session ".

I am connected to a network, but the database is stored on my local
harddrive, not on a network drive. I can disconnect from the network and
still experience the same problems.

Oddly enough, I copied the DB and loaded it on a Vista PC using Office2007
and the dates stayed the way they were entered. This leads me to believe that
there is some setting somewhere in access or in Win98 / WinXP that is causing
this problem.

The only thing left would be to set the date entry fields to current date
using =FORMAT(DATE(),"DD/MM/YYYY") and not allow changes. This, at least,
seems to work and most of the time the current date is correct anyway.

Thank you for your time and consideration.
--
Mortimer14

"Allen Browne" wrote:

I've used Access 98 (with Access 97 and earlier), and didn't have the
problem you describe, so I don't know what's going on. (The screenshot was
for Win7.)

Access will spin the dates around at entry time if it can't make sense of
them, so if the problem is occurring it makes sense that it would store them
that way.

I've no idea why your case is doing the weird thing. It's not like this
machine is actually running Access in a Terminal Server session or
something?

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"Mortimer14" wrote in message
...
I have confirmed that the input mask and format are blank.

I also confirmed that this isn't just a display problem, the dates are
being
stored in their altered form. E.G. Enter 7/12/2009 and the display
switches
it to 12/7/2009 and stores it in the table as 40006 which translates to 12
July 2009. Similarly enter 6/12/2009 watch the display switch it to
12/6/2009
and store it as 39976 (12 June 2009).

--
Mortimer14