Windows report viewers offer several advantages over their web based counterparts.
1. Print preview is available - this view displays to the user what the form will look like when it is printed. Not available in html or on report server.
2. Often times HTML rendered reports do not appear the same as they do when they are printed. This can be confusing for the user and the developer.
3. More feature rich tool set from which to work from. In my experience, features like multi column reporting seem to work when viewed from the windows report viewer, but not when rendered in html using the web report viewer.
4. HTML/Server reports do not render the same in Firefox and IE. They do when using windows based reports.
With a little bit of configuration, windows report viewers can be embedded in asp/web pages.
This offers the advantages of web availability and windows report viewer functionality.
The next several entries will provide a method to embed a windows report viewer in a web page.
The idea is :
1. Publish a report to SQL report server.
2. Create a windows report viewer project to view the report.
3. Create a wpf project to hold the windows report viewer.
4. Create a web page to hold the wpf project.
5. Set up certificate permissions to view web page
The end result is an xbap (which can be embedded in a web page for presentation) that can dynamically display any report based on its path.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment