Databases Reference
In-Depth Information
Area
Limitation
Alternatives
Actions
Reports don't support events
Reporting Services doesn't support an event
like Access does. I want to
model at the design level. However, calling a
count pages, rows, groups,
function in a property of a report item can have a
and report item values, and
similar effect. Code is called in the order that items
call custom code when these
are rendered: left to right and top to bottom. You
“events” are fired.
can use class module-level variables to manage
values within the confines of one report rendering.
Code variables aren't tracked
Parameters may be used like
QueryString
values
across multiple “postings” of
in a web page. When a user clicks on an item, the
an interactive report. I need to
Action target can use an expression, which calls a
keep track of values that are
custom Visual Basic function. This function can
modified by code as my user
receive one or more parameter values or variables
interacts with a report.
to process. The resulting value may be passed as a
parameter to the same report, effectively posting
back to itself with meaningful parameter values.
The parameters may be used in expressions,
modifying report and item properties to change
properties or sort, group, hide, or show items.
Report Recipes
As we have endeavored to solve various business problems, we've learned to do some interesting things
with Reporting Services. On consulting engagements, I often find myself in front of a client who is ask-
ing questions like “can you do this or that?” Almost inevitably, the answer is “yes,” but the question
becomes what the best method would be to meet the requirement. With a little outside-the-box thinking,
a lot of interesting things are possible. This may involve some custom programming, embedding report
items, or using customer application components in concert with Reporting Services.
In the following section, I've compiled a description of reporting challenges and solutions we've encoun-
tered, developing reports for our clients. For each “solution recipe,” I provide a brief list of skills, tech-
niques, and resources needed to apply the report feature. This should give you a good idea of how
prepared you may be to use the techniques based on your skill set and the level of complexity. Some of
these are easy to duplicate, whereas others require more advanced skills, which may include Transact-SQL
and Visual Basic programming. These are not intended to be exercises or step-by-step instructions. I have
made a point to provide enough information to demonstrate the concepts and techniques. However, to
implement these solutions you will need to apply the skills you learned in the previous chapters.
Greenbar Reports
Once upon a time, most reports were printed on special continuous-feed paper. This paper is fan folded,
with a perforation between each page, making it stackable in the input and output printer bins. The long
scroll of pages has pin-feed holes on each side to feed it through and align each row with the mechanical
print head. One of the common characteristics of this paper is that it has preprinted green bars for every
other row of data. In more modern reports, this format remains popular to help readers visually separate
each row of printed information. This typically involves using a light pastel background color for alter-
nating table rows.
Search WWH ::
Custom Search