RE-Use of Datasets, Params etc

Last Post 07 Mar 2007 01:31 PM by Haywood. 3 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
find_dba
New Member
New Member

--
06 Mar 2007 06:59 PM
Is there a way to reuse stuff in report services 2005? I find I'm using the same dataset in many reports and parameters as well. It's really slow and painfull. What about headers and footers also. I'd like to reuse these too as I can have the golbal.ReportName in there and all the details I need about user and run date.

So in a nutshell - is it posible to reuse stuff or is this product a nightmare?

Thanks!
Haywood
New Member
New Member

--
07 Mar 2007 01:31 PM
Look into Report Snapshots in Reporting Services.
find_dba
New Member
New Member

--
07 Mar 2007 03:04 PM
Thanks for your replies. Yes it seems copying reports is the quickest option to reuse the same datasets. It's a classic workaround.

What we need it the same setup as a data sources. Same with headers, footers and params. You need to be able to just pick them off of your predefined set(s). This is what .net is meant to be all about.

Report Snapshots are a point in time view of a report with data. Copy this into your BOL url...

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/88ccec81-ac65-4fcd-a03d-e6ae9fb548c3.htm

Regards
deadguy
New Member
New Member

--
18 May 2007 12:44 PM
The copying solution (kludge) has the disadvantage that if you ever need to change the format of your template report, there is no link that updates the reports you based it off of.

We're struggling with this very problem at my organization right now. The best solution that I have been able to come up with is to not use report headers at all, and to instead create subreports that act in the same manner. Then you use sourcesafe to share the header between all of your projects to keep them synchronized.

We create a template with the subreport embedded so that if we later update the header all of our reports will be updated as well.

This limits your design options if, for example, it is important that your headers be at the top of every page, as opposed to just the pages that start a new group.

We're also following a similar path with the report body, because many of our reports reuse components. This also has the additional advantage of not having to add every possible dataset to the template report.

We've had to do a lot of nested lists to get all this to work.

I hope that helps. I'm still looking for a better way to reuse the common elements of our reports so that future updates are propagated, Particularly one that simplifies getting the headers to the top of every page. so, if anyone has any bright ideas, please chime in!
You are not authorized to post a reply.

Acceptable Use Policy