https://bugs.documentfoundation.org/show_bug.cgi?id=147879
ady <adylo811...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |filter:xlsx
--- Comment #11 from ady <adylo811...@gmail.com> ---
(In reply to bunkem from comment #10)
> I wanted to rule out that there is a problem with the spreadsheet.
>
> 1) The file if saved to ODS shows the same #VALUE error when recreating the
> steps.
Not if you close the new file first, whether ODS or XLSX.
>
> 2) I opened the spreadsheet submitted with Excel 365. Excel deletes the
> columns and the formula calculates and shows the value correctly.
>
> Please note the formula in the cell W12 in the Excel screenshot and compare
> it to the formula in the Calc screenshot. The actual formula is correct in
> Calc even if it shows #VALUE.
Not when following the steps posted in comment 5. Those steps show that the
"Precedent" cells don't even have to move in order to trigger the problem in
column AC (that's the original column with the _first_ error, before deleting
other column(s)).
So, my experiences with attachment 178753 from comment 0 (using STR from
comment 5) have been slightly different than bunkem's.
1. Open the file with a recent version of LO (in my case, I tested with
7.6.alpha built this week).
2. Without changes, save the file with a different name.
3. Close the file. This is key!
4. Open the new file. Delete column AB. > No problem in any formula nor in the
calculated results.
* The original XLSX file is 12KB whereas the new XLSX file is 9KB in size.
* The result is independent of the file format (XLSX or ODS); the key is to
close the new file after saving with a new name.
>
> It would appear to me to be calculation engine issue.
* Re-saving, closing and opening the new file works correctly in the same
version of LO Calc. This is unnecessary with other spreadsheet tools.
I guess someone with enough knowledge of the XLSX format could check the
differences between the original file and a re-saved copy in order to find out
what's the difference that triggers the error, so it can be solved without
having to re-save and reopen the original XLSX file.
--
You are receiving this mail because:
You are the assignee for the bug.
