Issue 106083 - Error message "too many rows" when saving XLS file with new file name (save as)
Summary: Error message "too many rows" when saving XLS file with new file name (save as)
Alias: None
Product: Calc
Classification: Application
Component: save-export (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: oc
QA Contact: issues@sc
: 103215 (view as issue list)
Depends on:
Blocks: 99999
  Show dependency tree
Reported: 2009-10-20 11:55 UTC by Joost Andrae
Modified: 2017-05-20 11:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Joost Andrae 2009-10-20 11:55:11 UTC
All documents mentioned within this issue have been provided directly to Daniel
Renz. I cannot add them because they're confidential

The document is a XLS file, this file generate an error message
(second file) when saving the document.

To reproduce the problem :

1. open the file
2. save it as
3. In the dialog, choose a name and type it
4. don't change the format!!!
5. confirm saving by clicking on the "save" button in the dialog

You get the error message (see screenshot provided)

Root cause are the print ranges on second and following sheets. These are
defined to span the whole sheet area (65536 rows, 256 columns, A1:IV65536) in
Excel. On import into Calc, these ranges are expanded to Calc's full sheet area
(1024 columns, A1:AMJ65536). The export filter does not shrink them accordingly
but detects a cell range overflow and thus shows a warning.
Comment 1 daniel.rentz 2009-10-20 15:53:16 UTC
Comment 2 daniel.rentz 2009-10-20 15:55:38 UTC
back to QA

Solution is to not warn about print ranges that are too big. If there is some
real cell content that is truncated on export, this will be warned by the code
skipping these cells.
Comment 3 oc 2009-10-22 09:39:22 UTC
verified in internal build
Comment 4 Marcus 2009-10-26 14:25:07 UTC
*** Issue 103215 has been marked as a duplicate of this issue. ***