Are you suggesting I create n number of groups based on n number of accounts? If that's the case then it would be a problem because I don't know the number of accounts beforehand. I used 4 accounts as an example (A,B,C,D) but it could be more or less. Also, in this multiple group scenario, I would be grouping by the same column...Don't think this presents a problem but just wanted to be clear on that. My solution for it so far has been creating a subreport that uses the same JDBC connection, but it repeats the query and handles the summary grouping there. I feel like this is a redundant approach and have been trying to see if I can reuse the resultset from the master report in the subreport to avoid the repeated query. I placed the subreport in the title of the master and it comes out how I want it, Summary of account A Summary of account B ... Summary of account n Account A Details Account B Details ....Account n Details though I am still looking for a better approach.