How do I make the Report Viewer Control accessible?

0
0

Currently I am using the AspNetWrapper to wrap the SSRS ReportViewer Control.

What is the best way of making the Control accessible so I can call ReportView.PerformBack() for example?

I have created a toolbar in the main app which works fine if you use it to generate a fresh report each time with a set of Parameters.

However to preserve toggle settings I need to be able to call PerformBack(), which means the report needs to be accessible from the main app.

This was possible using VWG

A c# sample would be great.

Thanks for your help

Ewan

  • You must to post comments
0
0

Hi Luca

I don’t know how VWG coded their reporting module, but they managed to create some sort of persistence so I could from an external control call PerformBack on the report viewer control

If I attempt that using the ASPnetWrapper I get

Viewer control object is in a read only state so I am out of cycle

Calling this is the only way to move back to previous Toggle selections on an SSRS report.

Thanks for your help

Ewan

  • Luca (ITG)
    There is no persistence possible with ASP.NET controls. VWG probably caused a full postback on each event, which is a terrible solution. We had several projects with VWG crashing on very simple asp.net integrations because they also stored the entire view state in the http headers, which are limited in size and are not supposed to be used to store data…
  • Ewan Walker
    Hi Luca Understand how they got it to work. Thanks for your solution which looks like it will do the job
  • You must to post comments
0
0

Hi Luca

Actually I achieved it with VWG

if (bitDrill)
{
this.rptViewer.PerformBack();
}

I will Email You the VWG report wrapper files

Thanks

  • Luca (ITG)
    Use WrappedControl, the base class is T. The VWG file don’t have the PerformBack() method and there is no need to create it in Wisej since the base class is T => ReportViewer itself. A lot easier.
  • You must to post comments
0
0

All the ReportViewer methods and properties are already exposed and accessible on the wrapper object since it’s a template class.

You simply cannot call them outside of the asp.net page cycle, just like asp.net or vwg.

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.