A: 

There's apparently no way to do this, from what I've found. The workaround that I've implemented is to turn on caching and run a data-driven subscription to generate the report. There are some problems with this, namely that it doesn't always seem to prevent the user from having to reload the report.

A more robust way is to enable history and a batch process that changes default parameters and creates the report, cycling through everything like in a data-driven subscription, but maintaining external references to which report goes with which date and history ID. For instance, you could have a database table that tracks the report run time, report ID and parameter set, and query against it to know which to display based on your parameters.

paulwhit