Databases Reference
In-Depth Information
Server-Side Parameters
Although URL rendering is by far the easiest way to incorporate Reporting Services in your applications,
it does have some limitations. When you send information via a URL, it is very easy for a user to change
that URL or see what it is that you pass.
By using the Reporting Services Web service, you can easily hide the details of how you retrieve report
information. Parameters are passed through your code instead of the URL. This gives you complete con-
trol over how that information is retrieved without exposing it to the users. Let's take a look at your first
rendering application.
Rendering through Windows
In this section, we'll take a look at the mechanics of rendering using the Reporting Service Web service.
We are going to build a simple Windows application that returns a list of reports from the report server.
Once we have the list of reports, we'll use the Web service to return a list of report parameters. After
entering any report parameters, we'll render the report to a file. These steps will illustrate the main com-
ponents of rendering through program code.
Building the Application Interface
To start, you need to build your application interface. Let's start by building a simple Windows form; for
this example, I've added labels, text boxes, and buttons for basic functionality. Figure 12-8 shows the
design view of your form.
Figure 12-8
Search WWH ::




Custom Search