The idea of using the RANGE clause is the option I'd be most likely to use BUT...

This whole thing is running from within a framework created by another developer, and it's a VERY overly restrictive framework. One thing I really hate about it is that I don't get to call the REPORT FORM command myself, and therefore, can't use any clauses he didn't explicitly expose--which is none. That may change soon, as I'm working on a way to run reports externally from the framework, while still appearing seamless to the user.

Anyway, for now, I'll just always print the summary, since the client says that's acceptable. Thanks for all the ideas! I'm sure they'll be useful in the near future.