From e.World Technology:
What's new in this version:
Version 9.0.2 may include unspecified updates, enhancements, or bug fixes.
If your dataset have null values in any of the columns that you want to average then your averages will be incorrect because it calculates those cells as equaling zero. That's right. Zero. I complained to the programmers of this software over a year ago about this and they said "Thank you for your input. We'll consider in future versions (v6+)." Well they've gone through quite a few revs and not fixed this very serious problem. They seemed more concerned about making sure their graphs are pretty.
If you value accuracy and you're calculating averages then run, do not walk, but run away from this software as fast as you can. A shame too, because if fixed this would be great software, but systemic mathematical inaccuracies in a reporting software are inexcusable.
Updated on May 14, 2014
No that didn't fix it ... when you select that option it also skips zero values. You need to fix the software so it does a IsNull on each zero value when reading each value from the DB so it stores a null value or empty, not a zero. They are NOT the same thing. The problem still exists: it thinks null values are zero. THEY AREN'T.