<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Boyan Penev
»
Reporting Services Styles in a Database Table...
Reporting Services Styles in a Database Table
Rate Topic
Display Mode
Topic Options
Author
Message
Boyan Penev
Boyan Penev
Posted Thursday, March 26, 2009 12:26 AM
Grasshopper
Group: General Forum Members
Last Login: Wednesday, May 30, 2012 7:15 PM
Points: 22,
Visits: 121
Comments posted to this topic are about the item
Reporting Services Styles in a Database Table
Boyan Penev
Post #683860
markus.krenn
markus.krenn
Posted Thursday, March 26, 2009 3:19 AM
Grasshopper
Group: General Forum Members
Last Login: Tuesday, April 16, 2013 7:42 AM
Points: 12,
Visits: 58
Hi Boyan Penev,
why do you need parameters?
Your Resultset of the StoredProcedure has only one row containg the value of the colors. So, my meaning is that you can use an expression like this in the color-Property:
=First(Fields!HeaderColour.Value, "usp_CTL_Get_Report_Colours")
Then also the disadvantage of the parameters is eliminated.
With kind regards,
Markus Krenn
markus.krenn@plus-it.de
Post #683921
peterzeke
peterzeke
Posted Thursday, March 26, 2009 6:15 AM
SSC Veteran
Group: General Forum Members
Last Login: 2 days ago @ 1:32 PM
Points: 285,
Visits: 1,197
Interesting article... would it be possible to post the .rdl xml of an example to this discussion thread. I can't quite visualize it based on the article alone.
Post #684028
marty.zigman
marty.zigman
Posted Thursday, March 26, 2009 6:32 AM
Forum Newbie
Group: General Forum Members
Last Login: Thursday, October 08, 2009 6:29 AM
Points: 1,
Visits: 2
Why not store the properties in an XML document (database or filesystem) to allow for a larger range of properties and values to be defined without having to modify the database each time we want to centralize a style?
Post #684038
Dan Guzman - Not the MVP
Dan Guzman - Not the MVP
Posted Thursday, March 26, 2009 12:31 PM
Say Hey Kid
Group: General Forum Members
Last Login: Friday, April 26, 2013 11:57 AM
Points: 708,
Visits: 660
Markus - I get a scope parameter error when I try this. sp calls direct might not be allowed
correction ---- I got it to work, the second parameter is the name of the dataset, not the name of the sp. Good idea Markus.
Dan
Post #684480
Paul Hales-839333
Paul Hales-839333
Posted Thursday, March 26, 2009 4:45 PM
Forum Newbie
Group: General Forum Members
Last Login: Thursday, July 23, 2009 11:32 PM
Points: 3,
Visits: 13
Nice one Boyan. Always good to store your corporate colours / fonts / formats etc in a centralised location. You suggested a simple .Net management screen to potentially create, update, delete the "stuff" in your tables. An alternative (although not as sexy) which could be useful is to use Report parameters to perform this functionality to avoid the need for a .net app. Thats my 2c anywho. Keep up the good work dude
.
Post #684683
Martin N
Martin N
Posted Sunday, March 29, 2009 7:33 PM
SSC Journeyman
Group: General Forum Members
Last Login: Yesterday @ 10:43 PM
Points: 79,
Visits: 158
in order to get around the problem of one dataset per report item I was thinking you could just create a table valued sql function and join it to your report resultset, just format the function output to be one row with multiple col's.
Then you could just pick the fields and setup the styles
M
Kindest Regards,
Martin
Post #685841
noxidjkram
noxidjkram
Posted Tuesday, March 31, 2009 3:49 AM
Grasshopper
Group: General Forum Members
Last Login: Friday, November 02, 2012 9:53 AM
Points: 13,
Visits: 71
markus.krenn (3/26/2009)
Hi Boyan Penev,
why do you need parameters?
Your Resultset of the StoredProcedure has only one row containg the value of the colors. So, my meaning is that you can use an expression like this in the color-Property:
=First(Fields!HeaderColour.Value, "usp_CTL_Get_Report_Colours")
Then also the disadvantage of the parameters is eliminated.
With kind regards,
Markus Krenn
markus.krenn@plus-it.de
This would be fine if it was only to be used in the report body, but you cannot access datasets like this for headers and footers hence for these you would have to store them in parameters (or in hidden textfields in the main report area that were then accessed by name from the header and footer).
BR,
Mark
SQL Novice - Here to learn.
Post #686817
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
