On 9/8/05, Thomas Briggs <[EMAIL PROTECTED]> wrote: > > You (and I) may want an answer of 0, but I unfortunately believe NULL > is the correct answer. The answer isn't 0 - the answer is "there is no > answer", because there were no inputs. If that translates to 0 in > reality that's up to you to interpret. :)
Yeah, I've cursed nulls occasionally because I had to jump through hoops to get the results I wanted, but used them too when people wanted to know how many records had missing data. That's why we get paid the big bucks! ;)
