I may just be missing this, but I would like to build a multi-use report that can be filtered five different ways. For this, I want to include a number of filters set to Prompt, but I don't want to have to choose a value for each of them each time I run the report.

There are ways of making this work (using the "Select All" in a list criteria), but it is still a chore to go through when running the report. I'd like to run the report and include everything with a single click of "View Report," and only have to set parameters if I want to limit my results according to one or more criteria.

So far, I have never designed a report or seen a real report more than one page wide. I'm sure in other businesses such a thing is more common. For me, however, I am always in the position of fitting the most important data within a single landscape page width.

As such, adjusting the column widths in ActiveReports is a chore I must go through on every report I build. While I don't expect the software to magically size the columns perfectly, I would really appreciate an option to force the table to fit the page width. Then, rather than adjusting the width of the columns in inches, I'd adjust them as a percentage of the width of the page.

For reference, I use Excel's "Fit To" Scaling feature in their Page Setup on nearly every spreadsheet I print.

When adding a stored procedure to a model, we can assign parameters at runtime (i.e. prompts). That is a great feature. However, I have two issues with the way it is implemented:

1. A default value must be provided. If a report is created using the stored procedure, the report is run before the user is prompted for a value - when previewing the report. It would be helpful if the default provided while setting up the stored procedure could be set to require a prompt during preview. i.e. the default would only be used by ARS when running the SP for meta data. The user would be given the option to either use the default for preview or to require setting prompt options when used in a report.

2. It would be helpful to have the ability to set a relative date as a default for a date type parameter.

It would be great to be able to set a section such as the detail section, or a grouping to be kept together on the same page. This is helpful in the case where a section renders over multiple lines. For example, if a detail section spans 3 lines, it would not print at the bottom of the page unless the entire detail section fits. If it doesn't fit, it would go to the top of the next page. The same would hold for a grouping: if the whole grouping (including sub-groups and details) won't fit at the bottom of the page, then start at the beginning of the next page.