> it ends up being the total number of pages of the LAST data group processed on the report.

That's not what I'm seeing: The 3-page report appears somewhere in the middle of the 95 pages of output. There are mostly 1-page groups and a few 2-page groups in the report but all print as " of 3". --PageNo is always correct but _PageTotal always shows the value for the grouping with the maximum number of pages, regardless of where that group is in the batch. It does make me wonder exactly HOW the _PageTotal really works but, it really is irrelevant since it obviously isn't going to work for me.

In message #1321284 that Naomi mentions, you suggest 2 workarounds to someone with a similar problem . Running the report twice (once to file) isn't a great option: this process is already slow because of complicated data manipulation. But I'm not running SP2 either. I've been thinking about it but.... This application is scheduled to deploy any day. Adding SP2 would mean having to retest everything AND having to reinstall on every workstation. I guess I just have to decide which evil is worse. Are there are there enough benefits to SP2 to justify the pain?