Bug 105456 - Date Format MM/DD/YY not accepting 17 in YY position
Summary: Date Format MM/DD/YY not accepting 17 in YY position
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-20 17:50 UTC by Ray
Modified: 2017-02-05 02:49 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ray 2017-01-20 17:50:52 UTC
Description:
Does not crash. Dialog box appears stating "date invalid" with 01/19/17. 01/19/16 works in same cell. Cell formatted for MM/DD/YY.

Steps to Reproduce:
1.Select cell formatted for date MM/DD/YY
2.Input 01/19/17
3.Press ENTER key

Actual Results:  
Error dialog box appears stating "Date Invalid".

Expected Results:
Accepted the current year of 2017 and dropped down to next line.


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
Comment 1 Aron Budea 2017-01-20 18:06:51 UTC
Please check Date Acceptance Patterns in Tools -> Options...; Language Settings -> Languages, and if M/D/Y is there, cell formatting only affects output.
Then again, I'm not sure why it gives an error, for me it just isn't recognized as date if the entry doesn't match acceptance pattern.
Comment 2 Ray 2017-01-20 18:21:23 UTC
Did check the format selected and my selection was MM/DD/YY. This format has been in used in my spreadsheets for at least 3 years and has worked just fine until the current year. I just went and changed the format to MM/DD/YYYY and 2017 is accepted. Also checked other dates past '16' in the MM/DD/YY format and 18, 19  in the YY position is NOT accepted and the error dialog comes up as "Date Invalid".
Comment 3 Ray 2017-01-20 18:46:30 UTC
I did two things. First,I removed the direct formatting and reformatted the column I was using for dates; then I went to Options - LibreOffice - General - and changed the 'Year (two digit' range from "1936 to 2020" to "1946 to "2046". With these two changes I went back to the spreadsheet and enter the date for the entry as usual (01/19/17)and the year entry was accepted as typed. Weird. I also checked the "Accept date Format" under languages and made no changes, it did show 'm/d/y; m/d'.
Comment 4 Eike Rathke 2017-01-20 19:27:06 UTC
Whatever, "Date Invalid" is not a Calc message during cell input. More likely a validation or macro in your document bound to some input cells. Furthermore, the two digits year range quite certainly was not "1936 to 2020" because the range is always 100 years. Either 1936 to 2035, or 1921 to 2020, or something completely different. Maybe it was set to 1917 to 2016, which could explain why a validation macro said "Date invalid", because input of 17 lead to 1917 and the validation doesn't accept values before 19xx something.
Comment 5 Ray 2017-01-20 20:58:38 UTC
(In reply to Eike Rathke from comment #4)
> Whatever, "Date Invalid" is not a Calc message during cell input. More
> likely a validation or macro in your document bound to some input cells.
> Furthermore, the two digits year range quite certainly was not "1936 to
> 2020" because the range is always 100 years. Either 1936 to 2035, or 1921 to
> 2020, or something completely different. Maybe it was set to 1917 to 2016,
> which could explain why a validation macro said "Date invalid", because
> input of 17 lead to 1917 and the validation doesn't accept values before
> 19xx something.

I may have gotten the start date wrong but the ending was 2020. And there was a problem and is now fixed. Probably because I also removed the direct formatting and reformatted the cells. Funny how the problem just started with the change in year date. Sorry for taking up everybody's time. The first response was more help by suggesting an area to correct instead of telling me my problem was invalid. I think this will be the first and last bug report. Sorry again for the inconvenience.