It's not what I "want" Harlan, it's just what "is", or more correctly, what
Redmond says "is" should be.
I simply made an observation, stated a fact, and then voiced a preference.
A preference based on the operations of our offices importing a large amount
of pricing data, which sometimes is text, and sometimes is not.
The fact that the unary returns zero while the "old style" (how would you
label that Harlan) returns an error message, is another "Plus" in my book
for the "old style", since the zero doesn't really let you know if it
*really means* zero, or look at your data for "maybe" something wrong.
But, I'm sure not looking to debate you on this subject of which form is
better or worse.
Just stating an opinion.
--
Regards,
RD
--------------------------------------------------------------------
Please keep all correspondence within the Group, so all may benefit !
--------------------------------------------------------------------
RagDyer said:
<<"although Don's will fail if H2:H200 contains text">>
Is the connotation there Norman, that yours will add text?
The unary *ain't* that powerful!<bg>
However, while *both* will fail with alpha text, *only* the unary
fails with numeric text, which is why I've always favored the "old"
style.
....
All a question of whether you want SUMPRODUCT constructs to function like
SUM and SUMIF or like +. If SUM({1;"2";3}) == 4, why would it make sense for
SUMPRODUCT(({1;"2";3}>0)*{1;"2";3}) == 6?