Issue 72718 - Multiple Operations problem
Summary: Multiple Operations problem
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 2.1
Hardware: All All
: P3 Trivial with 5 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 97882 (view as issue list)
Depends on:
Reported: 2006-12-18 13:00 UTC by alan
Modified: 2019-08-13 11:07 UTC (History)
5 users (show)

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

SUM(x;y) - no error (95.54 KB, image/jpeg)
2006-12-18 13:02 UTC, alan
no flags Details
SUM(x:y) - error (107.09 KB, image/jpeg)
2006-12-18 13:03 UTC, alan
no flags Details
Spreadsheet with both examples (sheet 1 and sheet 2) (8.76 KB, image/jpeg)
2006-12-18 13:04 UTC, alan
no flags Details
Screenshot (65.73 KB, image/gif)
2006-12-23 11:26 UTC, kpalagin
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description alan 2006-12-18 13:00:13 UTC
When I choose a cell with a SUM function as the formula for Multiple Operations,
the results will only work for if the function is SUM(x;y), but not for SUM(x:y)
(with a range). See screenshots.
Comment 1 alan 2006-12-18 13:02:30 UTC
Created attachment 41511 [details]
SUM(x;y) - no error
Comment 2 alan 2006-12-18 13:03:16 UTC
Created attachment 41512 [details]
SUM(x:y) - error
Comment 3 alan 2006-12-18 13:04:20 UTC
Created attachment 41513 [details]
Spreadsheet with both examples (sheet 1 and sheet 2)
Comment 4 kpalagin 2006-12-23 11:25:42 UTC
Confirming with OO 2.1 on WinXP - if I change formula in cell A3 from "SUM
(C1+C2)" to "SUM((C1:C2)" calculation fails. 
I am attaching screenshot, where problematic formula is circled in red.
Comment 5 kpalagin 2006-12-23 11:26:47 UTC
Created attachment 41670 [details]
Comment 6 frank 2007-01-18 13:48:00 UTC
Hi Eike,

I think it's a double but could not find it. If so, please close otherwise
proceed as needed.

Comment 7 niklas.nebel 2009-01-09 10:12:21 UTC
*** Issue 97882 has been marked as a duplicate of this issue. ***
Comment 8 pfeffer2de 2009-01-09 13:20:27 UTC
very strange: alway someone says 'using ranges in Multiple Operation" doesn't 
work. But if you replace in the last posted example (
"MultipleOperationsExample.ods") in cell E16 the function "=match(0;D2:D14;0" 
by "=sum(0;D2:D14;0)", the sum is calculated correctly --> the reasons of 
failing must be more complex.
Comment 9 niklas.nebel 2009-01-09 13:54:40 UTC
pfeffer2de, are you mixing this up with issue 39304? That's a different problem,
and there the input cell D16 is used with a single-cell reference in D2.
Comment 10 pfeffer2de 2009-01-09 16:53:05 UTC
I'm astonoished about what is the difference of the problems.

issue 39304 doesn't directly reference the input cell by a range, but does so 
indirectly: the input cell is referenced by the output cell E16 by a function 
(originally "match", alternatively try "sum") by a range, which references the 
input cell.

--> ok, I tried: a generally workaround is: using inderect references to the 
input cell if you want to use a cell as input cell being in a range. E.g. 
instead of using "=sum(a1:a2)" in the output cell, entder in a cell B1 "=sum
(a1:a2)" and reference it by the output cell "=b1". That works.

Ok, then I understand, why you say, that it's a different thing: directly 
referencing the input cell as part of a range is not allowed (as in the issue 
39304), indirectly causes problems (only?) when lookup functions (is 
multiple.operation itself a "lookup funktion"?) are involved.

To summerize:
1. there are cases in which the multiple.operations functions works correctly.
2. you never can be sure that this is the case.

I suggest: remove this function or make it work correctly. It is absolut 
inaccaptable to get wrong results without being warned or even to know in which 
cases this happens. See my issue 96803 (
show_bug.cgi?id=96803 ).
Comment 11 honfui 2009-01-12 00:46:09 UTC
As said in issue #97882 that this is a limitation of current
implementation. So way forward, is it targeted for fix in ver. 3.1?
So far, I don't see that and this bug is more than 2 years.
Comment 12 Marcus 2017-05-20 11:13:09 UTC
Reset assigne to the default "".
Comment 13 lukaskoebis 2019-08-13 11:07:31 UTC
I just encountered the same issue. Are there any plans to fix this? Is MULTIPLE.OPERATIONS not a stable feature?

I also started a thread here: