DCOUNT in Excel: Numeric Observations Versus Matching Records

=DCOUNT(database, field, criteria)

The database range includes the header row. Field identifies the column to calculate: use a quoted heading such as “Units”, or its one-based position within the database. Here Units is field 3, even if the database is later moved to another part of the sheet. Criteria is a separate range containing matching field headers and at least one conditions row. Database and criteria are required. Field is optional for DCOUNT; the omission case is explained below.

Enter this mixed-value database in A1:D8:

Put Team in F1 and Product in G1. In F2 enter ="=North"; in G2 enter ="=A". These formulas produce the exact-match criteria text =North and =A. Type pending as ordinary text in C8 and leave D8 physically empty, rather than typing the instruction. F1:G2 selects four North/A records. Three Units values are numeric (2, 4 and 6), and the fourth is text; three Sales values are numeric, and the fourth is empty.

Conditions in the same criteria row act together with AND. Alternative criteria rows act with OR. Keep the criteria and output cells outside the database, and leave room for the data to grow.

=DCOUNT(A1:D8,"Units",F1:G2)
=DCOUNT(A1:D8,3,F1:G2)

Both have expected result 3. The ordinary text pending is not an additional numeric observation. A row can satisfy the Team/Product criteria while its target measurement is still missing or nonnumeric.

This count is the appropriate denominator control when averaging the three numeric Units values 2, 4 and 6. Using four matching records would instead divide their total 12 by four and incorrectly report a mean of 3.

=DCOUNT(A1:D8,,F1:G2)

Expected result: 4. The empty second argument position leaves field unspecified while retaining criteria in the third position. Microsoft’s description explicitly permits this, although its argument list inconsistently labels Field required. The omission rule is a documented feature, not a spelling shortcut.

Compare numeric count 3 with record count 4. Their difference, one, identifies a selected record without a numeric Units value. It does not identify whether the issue is intentional text, a blank, an error or another data-quality case without inspecting that record.

=DCOUNT(A1:D8,"Sales",F1:G2) also has expected result 3, because the selected Sales field has three numbers and one physically empty cell. The same numeric counts hide different missing-data forms: Units contains pending, while Sales is empty.

Keep DCOUNTA beside DCOUNT if the distinction matters. In this fixture, DCOUNTA on Units is four and DCOUNTA on Sales is three. Numeric coverage of Units is 3/4, or 75% of selected records.

That percentage is a chosen completeness measure. A numeric zero counts as a number, so numeric coverage alone does not establish that a measurement is plausible or complete.

In a separate copy, replace pending in C8 with the numeric value 0. DCOUNT on Units now has expected count 4, while the matching-record count remains four. The units total is still 12, but the mean over four numbers is now 3.

This demonstrates why filling missing measurements with zero changes the data model. A count function cannot decide whether zero represents a real observation or a placeholder.

A valid criterion selecting no records has a mathematical count of zero; this is a counting-model expectation, not a native error test. Invalid database headers, a field outside the range, or malformed criteria are different problems. The dedicated source does not establish every corresponding error code, so none is invented here.

Use the complete header-and-condition range, not just the condition cells. Check the field heading for spelling and spacing, and verify that a numeric field index still points to the intended column after a layout change. A worksheet’s visible rows are not a substitute for the explicit database range and criteria used in the formula.

Do not include an accidental empty conditions row in the criteria range: an unrestricted alternative can broaden selection. Microsoft’s DAVERAGE reference documents the shared AND/OR, exact-text and case-insensitive matching rules. These examples avoid wildcard, case-sensitive-formula and numeric-text complications.

The database functions do not validate whether the selected records are the right records for the question. Keep a matching-record or numeric-field count beside an important result. Native blank/formula-empty handling, coercion, extreme precision and error propagation not explicitly documented in this guide remain unverified.

• Current documentation: the dedicated Microsoft reference lists Excel for Microsoft 365, Excel for Microsoft 365 for Mac, Excel 2024, Excel 2024 for Mac, Excel 2021, Excel 2021 for Mac, Excel 2019, Excel 2016.
• Introduced: the first introduction version/build is not established by the dedicated reference used here.
• Last functioning version: unknown; a current help listing is not a last-working-build test.
• Evidence checked: October 15, 2026. Official documentation was freshly retrieved; examples were independently calculated. No native Excel, Mac or web-client execution was performed.

• Microsoft DCOUNT reference.
• Microsoft function catalog and introduction-marker explanation.
• Editorial testing standards.

Examples use English function names and comma separators. Expected numbers are rounded independent mathematical calculations; documented error expectations are labeled as such. They are not captured Excel output. All illustrative data and policies are fictional.