Attached an ods spreadsheet with in B3 =VLOOKUP(A4;Sheet2.$A$1:$B$65536;2) and in B4 =VLOOKUP(A4;Sheet2.$A$1:$B$65537;2) Steps: 1 - Save document as xls (MS 97/2000/2003) 2 - Close and open document > B3 shows correct value and B4 #REF! The original .ods does not have this problem
Created attachment 58758 [details] original ods
Created attachment 58759 [details] resulting .xls with #REF!
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
The problem is still present in 4.3.3.1, Linux. Related to, maybe even justified by, the fact that xls originally didn't support nRows > 65536 ?
Just to give one more feedback: the bug is still present in version 5.0.2. This is not only a visualization problem, consider this real example (happened to me yesterday): =IF(ISNA(VLOOKUP($B3,$'Check NoProd'.A$1:A$983040,1,FALSE())),"NO",VLOOKUP($B3,$'Check NoProd'.A$1:A$983040,1,FALSE())) It is a legitimate formula, coming from Excel 2010. After saving and reopening the document not only cell value displays #REF, but even the formula is altered: =IF(ISNA(VLOOKUP($B3, $'CheckNoProd'.#REF!$#REF!:#REF!$#REF!,1,FALSE())),"NO",VLOOKUP($B3, $'CheckNoProd'.#REF!$#REF!:#REF!$#REF!,1,FALSE())) And there is no way to detect the corruption quickly, you have to close and reopen the document. Data corruption undermines confidence in open source productivity software, at least for my boss ;-)
(In reply to Luca from comment #5) > Data corruption undermines confidence in open source productivity software, > at least for my boss ;-) Does Excel 97/2000/XP (the xls format..) save more than 65536 rows :) ?
It does not. However, the page stating so http://office.microsoft.com/en-us/excel-help/excel-specifications-and-limits-HP005199291.aspx (mentioned in bug 83746) seems to be gone.