Yeah, that's usually the better way, I'm finding out. It's just that the "report" is being output to a paper form, and I have to do a lot of wacky gymnastics with data from lots of different tables. It seemed easier to just load up some variables with the results...

>I usually try to keep heavy processing out of the report. What I usually do is use CREATE CURSOR to create a cursor with enough columns to hold the values I need in the report. I may include columns just to hold values for custom break expressions. Then I fill the cursor with the appropriate pre-processed values. Reports then are very basic - just dumping column contents onto the page. About the most complex things in my reports are setting up SUMs or COUNTs on group or report breaks.
>
>Preprocessing in a method or procedure is more flexible than relying on report constructs.
>
>Depending on how intense the report processing is, this approach also offers the advantage of doing the calculations only once if you REPORT...PREVIEW, vs. twice if you do them within the report itself.