This tool was built with SAP's Xcelsius. If a warning, "Error #XXXX" (where XXXX is
a number such as 2032), is displayed just click on OK to continue ... you might have to
do this quite a few times if you've left the Sentimeter running unattended as the lack of
error handling results in the error displays being "stacked" so that you have to click on
each one to clear the report. Just yesterday I had to click my way through about 480 reports
but the Sentimeter was stil running underneath that reporting mess.

This warning is the consequence of Xcelsius's terrible error handling of the underlying Flash
runtime errors whcih results in BI dashboards that are occasionally about as user friendly as a
cornered rat. This is an enterprise business intelligence platform? I sometimes despair at the
gap between what the market needs and what vendors like SAP give us ...

Another problem is that OpenAmplify, the engine that performs the linguistic analysis
can become unavailable (they had a recent DoS attack) and overloading of their server
can cause timeouts of my proxy script which result in missing data points.

I plan to reimplement the Sentimeter using different tools -- drop
me a line at sentimeter[at]gibbs.com to be notified when that happens ...