>There is not an option to remove groups at runtime in the Report Designer. I wrote an article for FPA or FoxTalk (I don't remember which) on how to handle variable grouping years ago, but it's not trivial.
>
>I have not used the product, but GENREPOX may be able to do this for you. And perhaps Stonefield's reporting tool does it too, but I don't think they're marketing it anymore.
>
>If you don't want to fool around with 3rd-party products, then by far the easiest and most straightforward solution is to just have 2 different reports and call the appropriate one, as you already mentioned. There's nothing kludgy about that... people have been doing that kind of thing for years and years and years.
>

Depends on your definition of kludge, I guess! :)

>One other thing you can do is have your "model" grouping dependent on the user. In other words, instead of grouping on Model, change the grouping to be IIF(user=nomodel,"",Model) or some such. Change all your report objects in that grouping to be removed if blank and set up a "Print When" for each of them to only print when the user is the appropriate one. This is more work in setting up the report, but you don't have to worry about maintaining 2 reports that essentially do the same thing.
>

This seems like the best solution. The group header and footer bands typically contain few controls, so it's not really that much extra work, and it would produce a much cleaner end result. Thanks for the tip.

>--Brad