Apache OpenOffice (AOO) Bugzilla – Issue 8955
Calc cannot save file with group and custom row and column print ranges set
Last modified: 2013-08-07 15:14:55 UTC
1) Choose menu command Format | Print Ranges | Edit... 2) Set "Rows to repeat" to $1:$2 3) Set "Columns to repeat" to $A. 4) Press OK. 5) Try to save the spreadsheet. Result: Error messages "Error saving the document Name.sxc: General Error. General input/output error.
Mike, thank you for using and supporting OOo. Please upgrade to the latest version of OOo and install using a multi- user install followed by a workstation install. You can find details about this procedure here: http://documentation.openoffice.org/setup_guide/index.html Unable to duplicate on Win NT 4.0 SP6a, OOo 643. Followed user instructions and the file save fine for me.
Sorry, I appear to have missed a step when I entered my original list. Between steps 4 and 5, please add: 4a) Highlight column B and click on the "Insert Group" button (2nd icon from the bottom in the toolbar at the left).
Mike, thanks for the update. Duplicated on Win2k server SP3, OOo 643c. Order is irrelevant. 1. Format->Print Ranges->Edit 2. Rows to repeat = $1:$2 3. Columns to repeat = $A 4. Select column B. 5. Press F12 ( group this column ) 6. File->Save or Save icon 7. Enter filename. OOo generates non-fatal error message. File is not saved. User summary Can't save spreadsheet with a Print Range defined
Hi Sascha, please have a look at it. Frank
Set the Target Frank
I will have a look at this.
should be fixed in OOo 1.0.3 and OOo 1.1
-
mh->fma: does the status new/fixed really makes sense ?
fma->mh: This behavior of IssueZilla occurs when reassign to a new owner by using internal tooling. It was a rfe of our internal employees to workaround many steps to reassign a new owner. IsuueZilla workflow: In status resolved/fixed you can't reassign, so you have to change the status, reassign and reset the status (3 steps). In our tool: You can reassign directly, but of course the status switched to new/fixed. This is for our internal workflow correct. Can't see a real problem in it.
fixed
closed fixed