Iron Speed Technical Forums
Sign up Latest Topics

  Author   Comment  

Posts: 1
Reply with quote  #1 


This document describes how I went about creating report viewers for SQL Server Reporting Services and Crystal Reports.



I became frustrated with continually deploying applications just because users needed a new report or a change of parameter. 

Our reports were written in such a way that a screen was written to prompt for report parameters and then the report would be called passing the parameters to it.  This would involve a lot of coding, testing and having to redeploy the application every time a new report was written or parameters changed.  For Crystal Reports it also meant having to deploy the applications on a 32 bit server because we couldn’t get the Crystal Reports run-time engine to run on a 64 bit server.

We decided to have the reports listed in a table and call the report viewer when the report was selected and pass the report name to it.  The report would prompt for its parameters rather than an ISD screen.  The report would pop up in either a Crystal Report Viewer or a SQL Server  Report Viewer.

See the attached word document for more.



Posts: 35
Reply with quote  #2 
I've worked on something similar to this for viewing Crystal Reports. 

My boss wanted a web app that allowed him to upload a report, specify the parameters, and limit access to certain approved roles. I developed an app that has Report, ReportParameter, ReportRole, and ReportFrequency tables. Each Report has a list of parameters related to it that can be changed by the user uploading/editing the report. They can specify whether it's a static value (such as Location='Canada'), or a dynamic value (Date=Today, UserID=LoggedInUser). They can also set a Frequency to the report on a per-role basis (IE: Daily, Weekly, etc). This allowed me to pass all the required parameters in the QueryString to a single report page that can display any uploaded report.

The end result is an app that allows an administrator to upload a report, specify parameters, roles, and report frequency per role, and activate it for the end user to see. All the end user needs to do is log into the app and see a list of all reports associated with them, categorized by Daily/Weekly/Monthly. I also captured the last time the report was viewed by them. this allows me to sort each category by the most overdue reports.
Mind you, this was a ton of customized code.
Previous Topic | Next Topic

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Download Iron Speed Designer

Terms of Service Privacy Statement