<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Cut/Paste doesn't force auto recalc; running totals incorrect" href="https://bugs.documentfoundation.org/show_bug.cgi?id=120013#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Cut/Paste doesn't force auto recalc; running totals incorrect" href="https://bugs.documentfoundation.org/show_bug.cgi?id=120013">bug 120013</a> from <a class="email" href="mailto:thatseattleguy@gmail.com" title="David Ruggiero <thatseattleguy@gmail.com>"> David Ruggiero</a> <pre>Updating on my own <a href="show_bug.cgi?id=120013#c3">comment #3</a> - - If <return> is not hit after the paste, running total column appears to be incorrect from the same row that the paste happened into, onwards. - If <return> IS hit after the paste, running total column appears to be recalculated only up until the same row as the *cut* occurred from; it's wrong after that. - Either way a force recalc is needed to insure correct results are displayed fully. I agree the $ static references are the key here. We often use running total columns (eg A$1:A${n} where 'n' is the current row) and see this same behavior often when using them.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>