DPRODUCT

Microsoft publishes this example with the description "The product of the yields from apple trees with a height between 10 and 16 feet and any pear trees" and the result $800. Derived independently: the first criteria row selects apples with 10 < height < 16 (only the Apple/14ft record, yield 10) and the second criteria row selects every pear (yields 10 and 8), so the product is 10 * 10 * 8 = 800. SIBLING PAGES DISAGREE ABOUT THE DOCUMENTED RANGE, AND ONE OF THE TWO READINGS CANNOT WORK. All six database-function pages in this batch (DCOUNTA, DPRODUCT, DSTDEV, DSTDEVP, DVAR, DVARP) print a byte-identical example table, but they cite two different database ranges for it: DCOUNTA, DVAR and DVARP write A4:E10 while DPRODUCT, DSTDEV and DSTDEVP write A5:E11 -- and DSTDEV repeats its version in prose ("if the data in A5:E11 is only a sample"). For that table pasted at A1 the database header row (Tree/Height/Age/Yield/Profit) is row 4 and the last record is row 10, so A4:E10 is the reading that works; A5:E11 starts one row BELOW the header, which leaves the field label "Yield" unresolvable and could not produce any of the six published results. Every one of those results is reproduced by the A4:E10 reading, which is the one used here (shifted two rows, as A6:E12). Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Microsoft documents the field argument as accepting "a number (without quotation marks) that represents the position of the column within the list". Column 4 of A6:E12 is Yield, so this must return the documented example's 800. Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Derived from the documented description, "Multiplies the values in a field (column) of records in a list or database that match conditions that you specify": the criteria block in H3:H4 (header Tree, condition Cherry) matches the single cherry record, whose yield is 9, so the product of the one matching value is 9. Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Derived from the documented description. Criteria A3:A5 is the Tree column header plus the two tree names, so it selects the five apple and pear records (yields 14, 10, 10, 8 and 6) and excludes the single cherry. Their Profit values are 105, 96, 75, 77 and 45, whose product is 105*96*75*77*45 = 2619540000 -- exact in IEEE-754 double precision (well under 2^53) but past the 32-bit integer range, so an engine that accumulates the product in a 32-bit integer overflows here while passing the small documented example. Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Microsoft publishes this example with the description "The product of the yields from apple trees with a height between 10 and 16 feet and any pear trees" and the result $800. Derived independently: the first criteria row selects apples with 10 < height < 16 (only the Apple/14ft record, yield 10) and the second criteria row selects every pear (yields 10 and 8), so the product is 10 * 10 * 8 = 800. SIBLING PAGES DISAGREE ABOUT THE DOCUMENTED RANGE, AND ONE OF THE TWO READINGS CANNOT WORK. All six database-function pages in this batch (DCOUNTA, DPRODUCT, DSTDEV, DSTDEVP, DVAR, DVARP) print a byte-identical example table, but they cite two different database ranges for it: DCOUNTA, DVAR and DVARP write A4:E10 while DPRODUCT, DSTDEV and DSTDEVP write A5:E11 -- and DSTDEV repeats its version in prose ("if the data in A5:E11 is only a sample"). For that table pasted at A1 the database header row (Tree/Height/Age/Yield/Profit) is row 4 and the last record is row 10, so A4:E10 is the reading that works; A5:E11 starts one row BELOW the header, which leaves the field label "Yield" unresolvable and could not produce any of the six published results. Every one of those results is reproduced by the A4:E10 reading, which is the one used here (shifted two rows, as A6:E12). Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Microsoft documents the field argument as accepting "a number (without quotation marks) that represents the position of the column within the list". Column 4 of A6:E12 is Yield, so this must return the documented example's 800. Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Derived from the documented description, "Multiplies the values in a field (column) of records in a list or database that match conditions that you specify": the criteria block in H3:H4 (header Tree, condition Cherry) matches the single cherry record, whose yield is 9, so the product of the one matching value is 9. Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Derived from the documented description. Criteria A3:A5 is the Tree column header plus the two tree names, so it selects the five apple and pear records (yields 14, 10, 10, 8 and 6) and excludes the single cherry. Their Profit values are 105, 96, 75, 77 and 45, whose product is 105*96*75*77*45 = 2619540000 -- exact in IEEE-754 double precision (well under 2^53) but past the 32-bit integer range, so an engine that accumulates the product in a 32-bit integer overflows here while passing the small documented example. Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Microsoft publishes this example with the description "The product of the yields from apple trees with a height between 10 and 16 feet and any pear trees" and the result $800. Derived independently: the first criteria row selects apples with 10 < height < 16 (only the Apple/14ft record, yield 10) and the second criteria row selects every pear (yields 10 and 8), so the product is 10 * 10 * 8 = 800. SIBLING PAGES DISAGREE ABOUT THE DOCUMENTED RANGE, AND ONE OF THE TWO READINGS CANNOT WORK. All six database-function pages in this batch (DCOUNTA, DPRODUCT, DSTDEV, DSTDEVP, DVAR, DVARP) print a byte-identical example table, but they cite two different database ranges for it: DCOUNTA, DVAR and DVARP write A4:E10 while DPRODUCT, DSTDEV and DSTDEVP write A5:E11 -- and DSTDEV repeats its version in prose ("if the data in A5:E11 is only a sample"). For that table pasted at A1 the database header row (Tree/Height/Age/Yield/Profit) is row 4 and the last record is row 10, so A4:E10 is the reading that works; A5:E11 starts one row BELOW the header, which leaves the field label "Yield" unresolvable and could not produce any of the six published results. Every one of those results is reproduced by the A4:E10 reading, which is the one used here (shifted two rows, as A6:E12). Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Microsoft documents the field argument as accepting "a number (without quotation marks) that represents the position of the column within the list". Column 4 of A6:E12 is Yield, so this must return the documented example's 800. Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Derived from the documented description, "Multiplies the values in a field (column) of records in a list or database that match conditions that you specify": the criteria block in H3:H4 (header Tree, condition Cherry) matches the single cherry record, whose yield is 9, so the product of the one matching value is 9. Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".

Derived from the documented description. Criteria A3:A5 is the Tree column header plus the two tree names, so it selects the five apple and pear records (yields 14, 10, 10, 8 and 6) and excludes the single cherry. Their Profit values are 105, 96, 75, 77 and 45, whose product is 105*96*75*77*45 = 2619540000 -- exact in IEEE-754 double precision (well under 2^53) but past the 32-bit integer range, so an engine that accumulates the product in a 32-bit integer overflows here while passing the small documented example. Set up from Microsoft's own worked example for the database functions: the orchard table, which is one criteria header row, two criteria rows, a database header row and six records. HARNESS PLACEMENT: the page pastes the table at A1, but this harness writes the formula under test into cell F1, which the table's second "Height" criteria header would occupy, so the whole block is pasted two rows lower instead. Every relative offset the page describes is preserved -- the database header is still the row immediately below the last criteria row -- which puts the criteria at A3:F5 and the database at A6:E12 here. One further deviation: the page writes its tree criteria as the cell entry ="=Apple" (the documented trick for storing the literal text =Apple, which forces an exact match). openpyxl cannot author that cell -- any string beginning with = is serialized as a formula -- so the criteria cells here hold the plain text Apple and Pear. On this data the two forms select the same records, because no other tree name in the table begins with "Apple" or "Pear".