>When I started out, my intention was to put three groups on the report, each with their own data in them, and then just hack the .frx to change what order the groups appeared in. The reason for this is that the user wants to change the sort order of the report, which affects how the groups are ordered. Since posting my original question, though, I've continued working on it and am far enough towards having it work with three reports that it would be more work to go backwards.

My favorite workaround for such reports was to have a few macros lying around, and then group on eval(group1), eval(group2), where group1, group2 would be variables keeping the actual group expressions. The same (or more of those) would be inserted as fields into group headers/footers as needed. Then it's just a matter of writing a good launching form, which would run the SQL, prepare the cursor (with variable filtering and ordering, again via macros) and run the report in the end. I once counted and found that this way I had one frx which counted like 48 reports (24 ways of ordering, plus a summary on/off option; didn't count the filtering here).