When I input 07/11/23, Access 97 automatically converts this to read
07/23/2023, I want it to read 07/23/1923. What should I do?

Please help! Debra Samuelson

Input 07/11/1923.

Access makes assumptions when you use 2 digt years. From 50 to 99 it adds
1900. From 00 to 49 and adds 2000. That's why you are seen 1923.

IMHO after the Y2K scare, any database developer worth their salt requires 4
digit years. Even then we are setting up for a Y10K panic!
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"Debra Samuelson" wrote:

> When I input 07/11/23, Access 97 automatically converts this to read
> 07/23/2023, I want it to read 07/23/1923. What should I do?
>
> Please help! Debra Samuelson

Actually, the assumptions Access makes are dictated by the operating system.

Go into the control panel, and look at the Regional and Language Options
applet. On the Regional Options tab, click on Customize. On the Date tab,
you'll be given an option to change how it interprets 2 digit years.

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


"Jerry Whittle" <(E-Mail Removed)> wrote in message
news:FD2A9E0B-1FFB-4C9E-A6EA-(E-Mail Removed)...
> Input 07/11/1923.
>
> Access makes assumptions when you use 2 digt years. From 50 to 99 it adds
> 1900. From 00 to 49 and adds 2000. That's why you are seen 1923.
>
> IMHO after the Y2K scare, any database developer worth their salt requires
> 4
> digit years. Even then we are setting up for a Y10K panic!
> --
> Jerry Whittle
> Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
>
>
> "Debra Samuelson" wrote:
>
>> When I input 07/11/23, Access 97 automatically converts this to read
>> 07/23/2023, I want it to read 07/23/1923. What should I do?
>>
>> Please help! Debra Samuelson