Description: I have a large spreadsheet of 153,000 rows with dates in Column A. When I save it and later reopen it, a couple dozen of those dates have been changed to zero, which is 30/12/1899, and I have to fix them in order for a graph to be right. Steps to Reproduce: 1. Save the spreadsheet 2. Reopen it 3. Actual Results: A couple dozen cells were zeroed. Expected Results: They should be the same as before. Reproducible: Always User Profile Reset: No Additional Info: The cells contained dates, not formulas. I don't know whether I should add the spreadsheet as an attachment, since it's 21 megabytes, but I guess I have to. I have another problem in this spreadsheet, which I mentioned in https://bugs.documentfoundation.org/show_bug.cgi?id=43983 but there has been no response.
Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon.
Created attachment 203632 [details] This is the spreadsheet with the problem. It's on Sheet1. Search for 30/12/1899.
Could this perhaps be a duplicate of Bug 165733?
Here are the dates that got zeroed in my spreadsheet: 17 Mar 1961 BC 17 Mar 1921 BC 16 Mar 1877 BC 16 Mar 1837 BC 15 Mar 1793 BC 15 Mar 1753 BC 15 Mar 1713 BC 14 Mar 1669 BC 14 Mar 1629 BC . . . 2 Mar 61 BC 2 Mar 21 BC My dates are separated by 10 days, so in the 20th century BC, I have March 17 in leap years only in 1961 BC and 1921 BC. So it's similar to "165733 – Some BC dates cannot be saved In Calc". It refers to the same dates. I don't really understand the English of user "bestive" in that one, but it seems that his or her problem with these dates was different.
I see now that the dates in question are dates which in the proleptic Gregorian calendar are February 29 -- "leap day". So some subroutine is trying to convert from the proleptic Gregorian to the Julian (which is what is displayed), and is messing up on every February 29th.
> dates which in the proleptic Gregorian calendar are February 29 That line made me reconsider the conditions described in Bug 165733 — and it turns out they match exactly. Although this report and Bug 165733 phrase the conditions differently, they are referring to the same thing: the bug occurs on the same specific dates.
*** This bug has been marked as a duplicate of bug 165733 ***
(In reply to Eric Kvaalen from comment #5) Thank you Eric - I see it's you who found out what was causing the problem. Thanks!
Thanks for fixing this! Now I wish someone would fix https://bugs.documentfoundation.org/show_bug.cgi?id=43983, as I mentioned!