Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On 20/04/2012, Regina Henschel <rb.henschel@t-online.de> wrote:
SUM( { NumberSequenceList N }+ )

e.g. SUM(a1+b2)

No. it would be SUM(a1;b2)


It would be better if calc returned an error, stating incorrect syntax


In LibreOffice the behavior of the operator + and the function is not
the same in regard of cells with no numerical content.

Your question is to general. Please give a more concrete example, what
you try to calculate, what your result is and what you expect the result
should be.


The question is general because a general understanding is required!
The example concerns only integers, e.g. where a1=1 and b2=2, the
results are correct, but the question is about learning the correct
syntax so that formula entered in a calc spreadsheet will not be lost
or corrupted when the spreadsheet is opened in another odf compliant
software, e.g. gnumeric. I don't want to use a sum syntax such as
(a1+b2), which gives the correct result, but if opened in another
program, the formula is lost or gives an incorrect answer.

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.