Description: as opposed to if you start new ods file, or open existing .xlsx file, and make file greater than 65k rows, if you then try to save as .xls file, it will warn you it's going to lose data when it saves. Steps to Reproduce: 1.if you open existing xls file 2.make it more than 65k row 3.save it Actual Results: it will successfully paste more than 65k rows, and you can work with it, but when you try to save the xls file, it will save without warning you it's going to delete rows beyond 65k. next time you load up xls file you find your data beyond 65k rows gone Expected Results: xls doesn't support more than 65k rows. if you start with ods file and save, it will warn you it's going to lose data. it should do the same when you try to save the existing xls that exceeded the limit. Reproducible: Always User Profile Reset: No Additional Info: ?
It simply warns you in general, that saving to an external file format may lose some information. A user may disable this dialog explicitly, but that means they know that they are doing. This is not a bug.
(In reply to frank48k from comment #0) > it will warn you it's going to lose > data. > it should do the same when you try to save the existing xls that exceeded > the limit. To be clear, there _is_ a warning, but it is just not specific to what exactly could be incompatible. In fact, the warning is there whether there is some incompatibility or not. The warning is about using a different file format other than ods. While there is no bug here, I think that the report is intended as an enhancement request (to warn users about very evident loss of data). I am not saying I agree with the request; I am just trying to clarify what I understand from comment 0 and when considering a prior related report from the same OP.
The case here: end-user opens XLS (with 65k limit). LibreOffice allows to use more rows (beyond 65k), even in case of XLS being opened. It throws away the additional data on save. Nicest thing would be that the range being limited to 65536 rows/ 256 columns on file-open of a XLS. So the end-user being unable to use more.
... and for CSV, it must disable row resize and insertion of charts and sheets; for TXT, it must disallow using different fonts or headers; for DOCX, it must turn off "Next Style" style feature; ... and so on - basically, becoming dozens different editors depending on an imported file's extension. I guess, it must simply stay read-only for PDFs, which we can's Save at all (we only can Export it). IMO, the description of export limitations in the *already existing* warning could be improved (see bug 125268 comment 37). But please no feature limiting based on file type - it is a wormhole.