Excel overrules Windows regional setting for two digit year translation

%3CLINGO-SUB%20id%3D%22lingo-sub-3208267%22%20slang%3D%22en-US%22%3EExcel%20overrules%20Windows%20regional%20setting%20for%20two%20digit%20year%20translation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3208267%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20is%20documented%20that%20as%20a%20rule%2C%20Excel%20will%20translate%20two%20digit%20dates%20either%20to%20the%201900's%20or%20the%202000'%20based%20on%20the%20breaking%20point%202029.%20So%20'30%20will%20become%201930.%3C%2FP%3E%3CP%3EWith%20that%20year%20only%208%20years%20in%20the%20future%2C%20it%20would%20seem%20that%20MS%20should%20reconsider%20this%20standard.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20also%20documented%20that%20the%20Windows%20Regional%20setting%20might%20overrule%20this.%20However%2C%20this%20is%20not%20the%20case.%20At%20least%20not%20for%20me.%20My%20setting%20(Control%20Panel%20%26gt%3B%20Region%20%26gt%3B%20Additional%20settings%20%26gt%3B%20Date%20%26gt%3B%20When%20a%20two-digit%20year%20is%20entered%2C%20interpret%20it%20as%20a%20year%20between)%20is%20set%20to%201950%20and%202049.%20However%2C%20from%201%2F1%2F30%20onward%2C%20the%20year%20will%20be%201930.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStrangely%20I%20cannot%20find%20any%20reference%20to%20this%20issue.%20I%20have%20supplied%20feedback%20to%20MS%2C%20but%20sharing%20it%20here%26nbsp%3B%20in%20case%20I%20overlooked%20something%20in%20advanced%20Excel's%20options.%26nbsp%3B%3CSPAN%20class%3D%22%22%3EExcel%20for%20Microsoft%20365%20MSO%20(16.0.14326.20702)%2032-bit%20%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3208267%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExcel%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3208704%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%20overrules%20Windows%20regional%20setting%20for%20two%20digit%20year%20translation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3208704%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F927277%22%20target%3D%22_blank%22%3E%40Kipopstok%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice%2Ftroubleshoot%2Fexcel%2Ftwo-digit-year-numbers%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EThe%202029%20Rule%3C%2FA%3E%3C%2FP%3E%3CP%3EIf%20you%20want%20to%20type%20a%20date%20that%20is%20before%20January%201%2C%201930%2C%20or%20after%20December%2031%2C%202029%2C%20you%20must%20type%20the%20full%20four-digit%20year.%20For%20example%2C%20to%20use%20the%20date%20July%204%2C%202076%2C%20type%207%2F4%2F2076.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDates%20in%20the%20inclusive%20range%20from%20January%201%2C%201900%20(1%2F1%2F1900)%20to%20December%2031%2C%209999%20(12%2F31%2F9999)%20are%20valid.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22%22%3E%3CSPAN%20class%3D%22%22%3E%3CSPAN%3EI%20don't%20know%20if%20this%20information%20will%20help%20you%20in%20any%20way%2C%20but%20I've%20included%20it%20as%20a%20notice.%20%3CLI-EMOJI%20id%3D%22lia_slightly-smiling-face%22%20title%3D%22%3Aslightly_smiling_face%3A%22%3E%3C%2FLI-EMOJI%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexcel-blog%2Fmeet-niko-chatzoudis-excel-forum-contributor%2Fba-p%2F2941385%22%20target%3D%22_blank%22%3ENikolinoDE%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20know%20I%20don't%20know%20anything%20(Socrates)%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

It is documented that as a rule, Excel will translate two digit dates either to the 1900's or the 2000' based on the breaking point 2029. So '30 will become 1930.

With that year only 8 years in the future, it would seem that MS should reconsider this standard.

 

It is also documented that the Windows Regional setting might overrule this. However, this is not the case. At least not for me. My setting (Control Panel > Region > Additional settings > Date > When a two-digit year is entered, interpret it as a year between) is set to 1950 and 2049. However, from 1/1/30 onward, the year will be 1930. 

 

Strangely I cannot find any reference to this issue. I have supplied feedback to MS, but sharing it here  in case I overlooked something in advanced Excel's options. Excel for Microsoft 365 MSO (16.0.14326.20702) 32-bit

4 Replies

@Kipopstok 

The 2029 Rule

If you want to type a date that is before January 1, 1930, or after December 31, 2029, you must type the full four-digit year. For example, to use the date July 4, 2076, type 7/4/2076.

 

Dates in the inclusive range from January 1, 1900 (1/1/1900) to December 31, 9999 (12/31/9999) are valid.

 

I don't know if this information will help you in any way, but I've included it as a notice.

 

NikolinoDE

I know I don't know anything (Socrates)

Thank you but no, the information is not helpful. The issue was specified as Excel overruling the Windows setting, with the undesired result. Typing a 4-digit date is a work-around, not a solution.

@Kipopstok 

The only thing I can suggest is to pre-convert the cells to text and use error checking to check for the century if necessary.

Or type an apostrophe (‘) before a number, example: '01.02.30.

The apostrophe does not appear in the cell after pressing Enter.

 

 

Thanks, but as said: I'm NOT looking for a workaround.
My question was rather specific if there was any Windows option I overlooked that is making Excel ignore the Windows setting. Because according to MS's own information Excel should follow Windows on this.

And anyway: adding the apostrophe is as much of a hassle as typing a 4-digit date. And by rendering the input to text you can't use formulas calculating the no. of days between two dates. And this is exactly the reason why the century actually IS relevant in the first place.

So thanks, but unless you have an answer to my question: "Is there a Windows option I overlooked that is making Excel ignore the Windows setting (contrary to MS's own design)", pls ignore this thread.