DCOUNT in Collabora Office: Count Numeric Fields or Complete Matching Records

• Introduced: the original Collabora release and launch date are not established by the reviewed sources.
• Availability: documented in Collabora Office 26.04 desktop help.
• Platform scope: online and mobile deployment support is not inferred from the desktop documentation.
• Checked: October 14, 2026. Function-specific documentation and independent controls; no native Collabora execution.

=DCOUNT(Database; [DatabaseField]; SearchCriteria)

Database and SearchCriteria are required. To omit the middle argument while still supplying criteria, retain the two separators: =DCOUNT(A1:E8;;G1:G2). The omission is explicitly supported by the Collabora reference; it is not a guess based on another database function.

Enter this database in A1:E8, including the header row. Cells marked leave empty must be physically empty; do not type those words or enter an empty-string formula. Enter pending as ordinary text.

Put the exact header Cost in G1 and the criterion >=10 in G2. The criteria range is G1:G2, including its header. It selects items A, B, F and G. Its column need not be vertically aligned with the database’s Cost column.

Use an empty output cell outside the database and criteria areas for each formula. Do not include unused rows in these criteria ranges. The database range includes all seven records, even though only four satisfy this first criterion.

With Cost >=10 in G1:G2, compare:

The selected Units cells contain 4, 0, 6 and an empty cell. Zero is numeric and counts. The Item values A, B, F and G are text, so they contribute no numeric field values even though their records match.

The difference between four matching records and three numeric Units entries is one. That is a completeness indicator for this field, not a claim that the missing value should be replaced with zero.

=DCOUNT(A1:E8;C1;G1:G2) and =DCOUNT(A1:E8;3;G1:G2) both have expected result 3, matching the quoted Units header. None changes the criterion, which still filters by Cost.

Selecting field four instead counts the four numeric Cost cells, giving 4. This demonstrates why filtering and selecting the measured field are separate steps.

Put Cost in G4 and H4, >=10 in G5, and <16 in H5. Use G4:H5 as the criteria range.

The same-row conditions select A, F and G, with costs twelve, fifteen and eleven. =DCOUNT(A1:E8;;G4:H5) gives 3 records; specifying Units gives 2 numeric values because G’s Units cell is empty.

Repeating the header is intentional. Putting the two conditions on different rows would change the logic to OR and select a different set.

Put Cost in G7, >=10 in G8 and >=15 in G9. =DCOUNT(A1:E8;;G7:G9) has expected result 4. Items B and F satisfy both conditions, but each record belongs to the selected subset only once.

Counting the two conditions separately and adding four plus two would produce six, double-counting those records. OR selection is not arithmetic addition of overlapping counts.

The ordinary text pending and physically empty cells in this fixture are not numeric. Formula-empty strings, numeric-text coercion and mixed errors are not comprehensively established by this small example. Use DCOUNTA for a separately defined nonblank-field count.

The shared reference documents invalid-header and field-index errors. It is safer to reference the exact header than to suppress such errors and assume a zero count. A no-match numeric criterion produces a count of zero by the documented counting contract; it is different from an invalid argument.

The field argument selects the column to calculate after records are matched; it need not be the column used in the criteria. It can be a quoted header, a reference to its header cell, or a one-based column index within the database.

For this table, Units, C1 and index 3 identify the same field. Index three means the third database column, not an absolute worksheet-column number. The shared help says a numeric field index ignores digits after the decimal point, but the examples use integers for clarity.

Criteria in the same row are combined with AND; criteria in separate rows are combined with OR. Repeating a header lets two conditions apply to the same field. Text matching and wildcard or regular-expression behavior depend on Calc’s calculation settings. The primary numeric criterion avoids those pattern choices.

If you use literal Team criteria, enable whole-cell matching and use the exact labels shown. Do not silently treat wildcard and regular-expression modes as interchangeable. The shared database documentation also treats dates and logical values as numeric in these functions; that rule should not be replaced with another aggregation function’s type rules.

• Collabora Office 26.04: DCOUNT.
• Shared database arguments and criteria rules.
• Editorial testing standards.

Complete function-specific and shared database documentation reviewed. Outputs are independent row-selection and arithmetic controls or explicit documented rules, not captured native results. Formulas use English names and semicolon separators.