Thanks for the suggestions. Turns out I'm doing about the exact same thing as you did. The user can choose the Sort, Group, and any fields available in the report to pull info on. I actually create a form on the fly that adds the fields they select and then allows them to put data in those fields to pull from the report. It's about the closest thing to a report writer that you can get without being one. I finally solved my grouping issue by adding the groups to the cursor I build and then in my report form group on the cursor. works fine.

Thanks again.


>
>My old Indian trick is to group on Eval(yourvar). Works happily for years. I have actually built a combination of one moverbox (to pick two or three items to order by, out of four or more), few textboxes to pick the filtering of the data, a combo to pick the report format (like summary / detailed / narrow / verbose) and then I use the filtering to create the Where clause of the SQL Select, mover values to create the Gr1, Gr2, Gr3, Caption1, Caption2, Caption3 for the reports, and to create the Order By clause of the SQL, and then run the report on the selected data. It comes down to at least 24 combinations (disregarding the filter) of ordering and reports - all with just 3 or 6 .frx files. I've noticed I have simply killed the older single-purpose reports and nobody complained.
>