Doug, two things to consider.... 1. Did you reset your variables based on the break. 2. Be sure and SET ZERO ON before running your report.
Gary ________________________________ From: Doug Hamilton <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Thu, November 18, 2010 8:53:18 AM Subject: [RBASE-L] - Re: Report Footer Variables compound Thanks Karen - I don't think DBCalcs will sum variables, only columns, but CMIIAW (Correct Me If I Am Wrong). And this anomaly is not in preview mode of report designer, it's the Print Preview from PRINT IFTACharge WHERE &vWheClause OPTION SCREEN. And now you've raised another question: Does Preview (as in Before Preview and After Preview EEPS) refer to Preview in Report Designer or the Print Preview with the OPTION SCREEN? Back to the original issue - I'd thought about creating a view with calculated columns so I could use DBCalcs vs summing variables, but that's going to be a time-consuming rewrite; I was hoping I'd just missed a click-box in Report Designer somewhere. D [email protected] wrote: Doug: AFAIK the report previewer has always acted that way. >The "old fashioned" summing variables (rather than DBCalcs), are >never cleared when you use the "preview" tab of the report designer >so they constantly double themselves. And they usually stick around >when you exit the report designer so you must clear them if you intend >on printing the report from outside the designer right away. As long as >those variables are initialized to 0, or cleared, before the report runs >you should be okay (to be sure, initialize them in the before generate). >Any reason you can't use DBCalcs instead? > >Karen > > > >I (think I) know it's because the variable totals aren't being cleared, >>but I can't figure out how while staying in the preview mode. >>The larger questions is why are they compounding? I thought once a >>report was generated for preview, the static results were displayed. >>But the report appears to be recalculating on next/prev page and when >>sent to a printer. The printed report is correct - most of the time; >>client says sometimes not, but I haven't taken the time to confirm. I >>figure once I get the problem resolved in preview, the printed report >>will be OK.
