Issue 98329 - inappropriate semicolon in SUBTOTAL() help for Calc
Summary: inappropriate semicolon in SUBTOTAL() help for Calc
Status: CLOSED FIXED
Alias: None
Product: documentation
Classification: Unclassified
Component: Online help (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: formulavxd
QA Contact: issues@documentation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-21 20:32 UTC by formulavxd
Modified: 2009-02-25 10:29 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description formulavxd 2009-01-21 20:32:09 UTC 
If you look in the online help for the SUBTOTAL() function in Calc, the example
is wrong. There should be a comma in the formula instead of a semicolon. If you
use the example as-is you get a 508 error code in your spreadsheet.

The help reads as follows:

Example
You have a table in the cell range A1:B5 containing cities in column A and
accompanying figures in column B. You have used an AutoFilter so that you only
see rows containing the city Hamburg. You want to see the sum of the figures
that are displayed; that is, just the subtotal for the filtered rows. In this
case the correct formula would be:
=SUBTOTAL(9;B2:B5)


The formula as given won't work but =SUBTOTAL(9, B2:B5) does work.
Comment 1 formulavxd 2009-01-21 21:50:37 UTC 
This appears to be a global issue in Calc formulas. All examples in the online
help use semicolons instead of commas, and all semicolons in formulas yield
vague error codes when utilized.

Therefore everyone should just use commas instead.

This is then not a bug but an issue for the whole Calc formula-handling routine:-(
Comment 2 Uwe Fischer 2009-01-22 08:57:31 UTC 
Please tell us in which version on which platform by which distribution you
found this.
Comment 3 Uwe Fischer 2009-02-25 10:29:14 UTC 
This seems to be an Ubuntu bug --> closed