https://bugs.documentfoundation.org/show_bug.cgi?id=161763
--- Comment #10 from [email protected] --- (In reply to ady from comment #3) ... > Or, if possible, just use an additional column ("discount") as part of the > original initial table, instead of having it in an independent table on a > different worksheet. > I have to repeat myself here: this completely defeats the purpose of using a multiple-spreadsheet-capable program. There are infinite reasons why one would need to have the discount column in a separate table while keeping it linked to the 'original' table. Yes, one can argue and discuss different ways of doing it, more or less efficient, more or less readable, etc. But the case I pointed out results in a plain wrong calculation (not a matter of opinion), a silent mistake that would probably be impossible to detect in a large table. I guess what I am trying to say has two parts: FACT: with the 'Update references when sorting range' enabled by default, a 'normal' user will end up with the 'chair' cell (tab 'discount', cell C4) being calculated using the price of the pillow!! (tab 'initial', C2). This is clearly a mistake. OPINION: What is the cause of that mistake? A) A misuse of Calc? (Note I am not referring to a sub-optimal use which would lead to less efficient workflow, etc. but a MISUSE, that would translate into a MISTAKE). In this case, it would be nice to learn what is the 'correct' use (and again, I am not referring to 'put the column in the same tab' or 'use =$tabname.$C$2' solutions because they obviously defeat the purpose of using a spreadsheet). B) An incorrect default option (enabled) of 'Update references when sorting range' option? C) Something else that I am missing entirely? If A) is the reason, then I would be surprised to find out what the 'correct' use of Calc is. If B) is the reason, well, there must be a good justification that this conversation is missing up to now. I agree that it would help to know - what is the default behavior of other spreadsheet programs - why that option exist in the first place Maybe someone from the developers' team can chime in? Or even better, the UX team (to comment on why this is the sensitive default behavior). -- You are receiving this mail because: You are the assignee for the bug.
