Bug 53149 - FILESAVE as .xls with SUM() with more than 30 comma separated summands does not modify this function
Summary: FILESAVE as .xls with SUM() with more than 30 comma separated summands does n...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.0.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-06 06:04 UTC by Rainer Bielefeld Retired
Modified: 2015-04-01 14:52 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Bielefeld Retired 2012-08-06 06:04:27 UTC
This is a spin off from "Bug 44817 - FILEOPEN .xls, SUM() with more than 30 comma separated summands cell should show formula + value instead of error message"

Steps to reproduce:
1. Open attached sample document"test10.ods"
2. Save as "test10.xls" and close
3. reopen from recent documents
   Cell C31 shows #NV or similar, formula is no longer visible

Some investigation with a text editor shows that the formula in C31 still is intact, but LibO denies to show the result because of Bug 44817

The problem is that that LibO accepts the SUM() for FILESAVE as .xls, but not for FILEOPEN .xls

Same behavior with LibO 3.3.3 amd OOo 3.1.1, so this seems inherited from OOo

I still have to learn more concerning our save as .xls policy before I decide whether this Bug needs a fix. But together with Bug 44817 LibO behavior is inconsistent.
Comment 1 Sören 2012-12-26 20:07:23 UTC
I still observe this error/inconsistency in
Version 4.0.0.0.beta2 (Build ID: 4104d660979c57e1160b5135634f732918460a0)
on Ubuntu 12.04 (x86)

using the files attached to Bug 44817
Comment 2 ign_christian 2014-07-22 09:25:54 UTC
(In reply to comment #0)
> 1. Open attached sample document"test10.ods"

Hi Rainer.. That file isnt here, nor in Bug 44817
Comment 3 QA Administrators 2015-02-19 04:42:26 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

Message generated on: 2015-02-18
Comment 4 QA Administrators 2015-04-01 14:52:25 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

-- The LibreOffice QA Team This NEEDINFO Message was generated on: 2015-04-01

Warm Regards,
QA Team