thanks, i will probably make multiple copies. Im the only one changing things, so its not a function of version control, just a headache to make sure all copies stay updated.
Is it just me, or isn't this something that you would think should be do'able? I keep running into limitations that seem pretty basic when you do real world reporting, most especially when things are not fixed and still in development, which is pretty much all the time at the beginning of a project.
the whole idea of parameters is to enable reports to satisfy a host of potential scenarios, why wouldn't the same report run with different parameters be an option within a single publication.
The other thing that is hard to swallow is having a full set of production scheduled reports and/or publications that have to be redone from scratch because the underlying SQL changed. Makes things very unstable when there are complex schedules to be reworked, just because a new parameter or field had to be added to the report.
Sorry, for the rant, thanks for your help