Maintain Report State

I have a matrix report where the user can drill down into a hierarchy to view
data for a particular product. The report also includes a parameter list
allowing the user to change the selected product.
The problem with this approach is that the user may drill to a specific
branch and then decide to switch products. At that point the report refreshes
and collapses back to the root node, because I have defined the report to
hide all groups on first entry.
Given that I am using Report Manager with no custom front end, does anyone
know of a good strategy to maintain state so that I can retain which groups
are expanded and collapsed for a particular user between instances of the
report?Modifying the Report Parameter causes the query to be executed. When this
happens the report is rendered from scratch. Hence you will not be able to
maintain the state of how the groups are displayed.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dave Morrow" <DaveMorrow@.discussions.microsoft.com> wrote in message
news:413E2C03-1362-4130-A16B-F7E371D2E0F3@.microsoft.com...
>I have a matrix report where the user can drill down into a hierarchy to
>view
> data for a particular product. The report also includes a parameter list
> allowing the user to change the selected product.
> The problem with this approach is that the user may drill to a specific
> branch and then decide to switch products. At that point the report
> refreshes
> and collapses back to the root node, because I have defined the report to
> hide all groups on first entry.
> Given that I am using Report Manager with no custom front end, does anyone
> know of a good strategy to maintain state so that I can retain which
> groups
> are expanded and collapsed for a particular user between instances of the
> report?

MAIL on SQL Server 2000 Standard on Windows Server 2003 64-bit

I've read about 2005 Enterprise Edition 64-bit and 2000 Enterprise Edition 64-bit and those mail issues. But, my particular situation is running SQL Server 2000 Standard Edition (32-bit) on Windows 2003 Server (64-bit). I got the mail profile set up ok for the SQL Server Service Account using Outlook 2000 and can send and receive mail using Outlook. But, even after restarting the SQL Server Services, there's no profile to choose in the SQL Mail or Agent Mail drop-down box. I have tried ON the server and remotely. Locally, the drop-down box doesn't even really 'drop down'. Remotely, I get the drop-down but it is empty. I don't need a primer on configuring SQL Mail for SQL 2000. I just need to know if this combination of SQL Server Editions and OS Editions will even support SQL Mail. Maybe adding the appropriate values in the registry will enable me to use this mail profile for SQL Server?
What about that smtp client that's out there. I've not used it on any machine and don't want to make this goofy one the guinea pig if it hasn't been proven to work.
No, we can't go to SQL Server 2005 yet on this server. It hosts a purchased system that isn't supported on SQL Server 2005.
Thanks for your help,
Michelle
I rebooted the server and was able to configure the mail profile and select it from my client/enterprise manager. It seems like things generally require a reboot more often on this server than I've experienced on other servers. I tested agent mail, xp_sendamail, and dts send mail tasks all to success. Now I'm fighting with installation of the SQL Server Health & History Tool.
Just wanted to document that sql mail DOES seem to work with this configuration. Keep trying and I'm sure that you'll get it to work, too :)