Forum Discussion
Excel overrules Windows regional setting for two digit year translation
- May 27, 2024
Default setting (1950-2049) in Windows 11 doesn't work from the box, we need first to "activate" it. Change on 1951-2050 or whatever you prefer. Apply. After that you may return back to 1950-2049 and apply again. It shall work now, 30 goes to 2030. Not necessary to restart Excel after the setting is applied.
From Chat GPT:
Excel has its own way of interpreting two-digit years. By default, Excel uses a cutoff year of 2029. This means that two-digit years from 00 to 29 are interpreted as 2000 to 2029, and two-digit years from 30 to 99 are interpreted as 1930 to 19991.To change this behavior, you can adjust the settings in the Windows Control Panel:Open the Control Panel.Click on "Clock and Region" and then "Region."Go to the "Formats" tab and click on "Additional settings..."In the "Customize Format" window, go to the "Date" tab. Change the "When a two-digit year is entered, interpret as a year between" setting to your desired range.This should help Excel interpret the two-digit year 31 as 2031 instead of 1931
Thank you, but this is NOT the answer.
a) the fact that ChatGPT refers to 'Clock and Region', while in Windows 11 there is only Region is already interesting.
b) In my original question, I already indicated that the current Windows setting is 1950-2049. So '30 should be translated into 2030. The problem is that Excel doesn't follow Window's own logic, even though the settings are that it should.
So if you take the time responding, then please read the question carefully and check if your answer works. Because I doubt if you try it on your own machine, it would. Quoting AI without fact checking is not the way to go.
- RajoFeb 28, 2025Copper Contributor
Don’t doubt people who try to be helpful!
The reason for posting was that I had the problem and I solved it, by using the tip from Chat GPT. It was convenient then to copy the tip from Chat GPT.
- KipopstokMar 04, 2025Copper Contributor
I stand corrected that you did try the solution and it worked for you. Nice!
However, the settings you offered as a solution were the settings as I already had them, and that didn't work for me. As I had specified in my initial question.
So trying to be helpful - check . Reading carefully to ensure you provide a relevant solution - open for improvement 😉