Hey Folks,

I just noticed something strange on the TOTAL row of a tabular report. I have 5 columns in this report. The first is hidden for sorting purposes, the second is just textual, the others are all numbers. I show the total for those three number columns. The 3rd and 5th are fine, but the 4th is showing a negative number. It makes no sense, because there are no negative numbers in that column. Moreover, if I run it as an active report and calculate the sum for the 4th column (by left clicking the column and selecting Calculate > Sum), then it calculates it correctly. Any idea why the total row is showing a negative number? And the number doesn't seem to make sense either, like its not the correct sum multiplied by -1 either, just seems to be a random negative number.

Here is the code:

TABLE FILE COST_OF_CALLS
SUM
     CNT.DST.CALL_SOURCE_KEY/D12 AS 'Calls'
     COMPUTE RESPONSE_TIME/D9C = DIFSEC/60/60; AS 'Total,Hours'
     COST_ON_CALLS/D12M AS 'Cost of,Calls'
  BY TOTAL HIGHEST COST_ON_CALLS NOPRINT
  BY BY_DISPLAY AS '&BY_DISPLAY_TITLE'

WHERE MONTH_YEAR EQ '&MONTH_YEAR'
ON TABLE SUMMARIZE
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE PCHOLD FORMAT AHTML
ON TABLE SET HTMLEMBEDIMG ON
ON TABLE SET LINES 700
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
GRAPHTYPE=DATA,
     COLUMN=N5,
$
TYPE=TITLE, COLUMN=N3, JUSTIFY=RIGHT,$
TYPE=TITLE, COLUMN=N4, JUSTIFY=RIGHT,$
TYPE=TITLE, COLUMN=N5, JUSTIFY=RIGHT,$
END

I realize you will not be able to run that code, sorry. But it might be helpful.

Also, in case this is important, the 4th column shows -579,182 on the TOTAL row. When I do Calculate > Sum, I get 613,871.


Thanks folks!

This message has been edited. Last edited by: Shingles,

Might this be an overflow issue? Doesn't seem like the right way to deal with overflows though...

NVM... it was an overflow issue. I moved the COMPUTE to a define and then things were great!

You know the difference between a COMPUTE and a DEFINE ?

COMPUTEs are evaluated after aggregation and sorting (but before TOTAL)
DEFINEs are evaluated at time of data retrieval.

This is important depending on the calculation you need.

So your DIFSEC field when calculated in a COMPUTE will be summed before the /60/60.

Also D fields are handled differently to other numeric fields like P fields.

Yes, I was aware... just forgot.

I know what you mean.

So much to remember.

I did remember in the end though... anyways... thanks Waz!

Could any of your DIFSEC values be nulls?

T