The report is based on a permanent table. But there are a dozen spots in the report where it prints a variable. For each customer, there's code before the report prints that determines what those dozen variables are. So I would have to either (a) load those variable values into a temp table that I can lookup from the report based on the CustID, or (b) do all those calculations within the report itself. The latter would probably have to be done by calling stored procedures because the code is really complicated. Or if it was upgraded, it would have to be done in one of the report band's before generate eeps.
Karen > Why do you have to recode to create a temp table? > > >> ----- Original Message ----- >> From: [email protected] >> To: RBASE-L Mailing List >> Sent: Tuesday, March 24, 2009 3:52 PM >> Subject: [RBASE-L] - Re: Printing a whole buncha reports >> >> >> Bernie: I might have to do that. As explained before, the report is >> meant to print for only one customer at a time because the program code does >> alot of calculations and variable setting before it prints the report. If I >> re-code the program so that I can have a temp table with all my data in it, >> then I can add a break column for the CustID in my report, and then be able >> to >> print either one big report, or break it into manageable chunks, as you >> say. I am also in favor of putting break pauses in there. But I first >> have >> to do alot of program re-coding to get there. >> >> Karen >> >
