Page Borders

We're creating a text report (i.e. not tabular, etc.) that will run several
pages. We would like to have a border around each page, including the page
header and page footer. We've set a body border, but that doesn't draw
horizontal lines at the top an bottom of each page.
We've tried putting our controls in a rectange and expanding the rectange to
be encompass a page both vertically and horizontally, but the page header is
excluded from this border (plus we suspect we'll have additional problems if
our individual controls causes a page break). Also, though we have the
rectange control's height set to 9 inches, it shrinks such that it ends
after the last control in the region.
Any suggestions for defining a border on each page, the first page excluded
(it's a cover page)?
We're using MS Reporting Services 2005.
Thanks,
ChrisNot sure if this does exactly what you're looking for, but in addition
to the body border, have you tried putting horizontal lines in the page
header & page footer?
Eva Pierce Monsen|||Thanks for Eva's informative inputs,
Hi Chris.
As Eva has mentioned, you can explicitly customize the SSRS report's header
and footer sections in the VS 2005's report designer. Just right click on
the report designer's empty area and you'll find the "Page Header" and
"Page Footer" option in the context menu, select either one to edit the
template.
#Adding a Page Header and Footer to a Report
http://msdn2.microsoft.com/en-us/library/ms159677.aspx
BTW, as for the body's border setting, based on my local test, it also
works (display both horizental and vertical lines). I simply set the border
width and border style (solid) and the runtime report displays both
horizental and vertical border lines for the report body. I think the
problem you met is possibly specific to report body's size.
Hope this helps.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Steven,
The horizonal body borders appear when we first render the report. However,
when we export the report to PDF, the horizontal lines at the top & bottom
of the body do not appear. Also, the border does not encompass the header
and footer, so even if the horizontal lines did appear, it isn't quite what
we're looking for. The prototype I'm working off of is a MS Word document
that has a page border that does encompass the header & footer.
Any other suggestions?
Thanks,
Chris
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:NasHAxdjGHA.4528@.TK2MSFTNGXA01.phx.gbl...
> Thanks for Eva's informative inputs,
> Hi Chris.
> As Eva has mentioned, you can explicitly customize the SSRS report's
> header
> and footer sections in the VS 2005's report designer. Just right click on
> the report designer's empty area and you'll find the "Page Header" and
> "Page Footer" option in the context menu, select either one to edit the
> template.
> #Adding a Page Header and Footer to a Report
> http://msdn2.microsoft.com/en-us/library/ms159677.aspx
> BTW, as for the body's border setting, based on my local test, it also
> works (display both horizental and vertical lines). I simply set the
> border
> width and border style (solid) and the runtime report displays both
> horizental and vertical border lines for the report body. I think the
> problem you met is possibly specific to report body's size.
> Hope this helps.
> Regards,
> Steven Cheng
> Microsoft Online Community Support
>
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Hi Chris,
Thanks for your response.
Yes, the body border solution has its natural limitation since it does not
include the Header and Footer sections. Have you tried Eva's suggestion on
customizing the UI through the Header and Footer template in the report
designer? As I've also mentioned in the previous message, you can right
click on the report designer's empty area and you'll find the "Page Header"
and "Page Footer" option in the context menu, select either one to edit the
template. Thus, you can put some report item(such as Line ) into the header
or footer section to simulate a border line. How do you think of this?
Regards,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hey Chris,
How are you doing on this issue, does the further suggestion help you some?
If there is still anything we can help, please feel free to post here.
Regards,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Padding Issue

We are creating hierarchical report showing line of sight for given Organization. The report data is tree structure. Each node is a row in the report. Each row in the report is nested by using padding expression. Padding expression is based on Node Level. When we print report or create PDF padding is removed and all the rows appear aligned. It looks like reporting Services treat padding as white space. We tried several options like using gif images and rectangle but failed.

The report appears fine when we export to Web Archive, the working sample and sample with issue are as attached.

This issue occurs both in report viewer control and report services url.

Does "Padding expression" mean that you insert whitespace based on the node level?

There is another way of doing this: Every textbox has a Padding.Left property. Assuming that the node level is available as a numeric field value, you could set the Padding.Left property dynamically: =CStr(4 * Fields!NodeLevel.Value) & " pt"

-- Robert

|||

Thanks for the reply

I have tried both padding.left and padding.right. When report is rendered padding appears fine but on print or export to pdf, padding is removed.

|||

Which version of Reporting Services are you using? Did you install the latest service packs for that version?

-- Robert

Package variables "disappear" from job properties

Creating a SQL Agent job to run a package works just fine. On the Step Properties, Set values tab, I can add variables and the values I want for them, no problem. The job runs just fine. If I want to go edit the values however, they're always gone.

Is there some security setting that hides the variables and their values which is on by default?

GregsListAcct wrote:

Creating a SQL Agent job to run a package works just fine. On the Step Properties, Set values tab, I can add variables and the values I want for them, no problem. The job runs just fine. If I want to go edit the values however, they're always gone.

Is there some security setting that hides the variables and their values which is on by default?

Greg,

I don't know the answer to this but regardless, you should stop using the SSIS sub-system and just call teh package usinng the command-line sub-system instead.

There is an article at wiki.sqlis.com that explains the rationale behind this but the site is down so i can't link to it. Basically you don't get any diagnostic info out of the SSIS sub-system.

-Jamie

Package Validation Error + Code 0xC004801C

Hi,

I am learning to use SSIS for creating packages. I am getting the following error when I try to execute my package...

Package Validation Error

Error at Data Flow Task[DTS. Pipeline]:The "runtime connection "FlatFileConnection "(122)" in the connection manager collection, Connections, of component "Flat File Destination ("120") does not have a value for the ID property. Verify that the ConnectionManagerID property of the runtime connection object has been set for the component.

Error at Data Flow Task [DTS.Pipeline]: component "Flat File Destination" (120) failed validation and returned error code 0xC004801C.

Error at Data Flow Task[DTS.Pipeline]: One or more component failed validation.

Error at Data Flow Task: There were errors during task validation.

(Microsoft.DataTransformationServices.VsIntegration)

I'd appreciate if someone can help me with this. Do I need to change some settings? Also, what does the number in brackets indicate, say in FlatFileConnection(122)? Is it valuable information while debugging?

Just to give an idea, my package is like this -

source FlatFile -> Derived Column -> Lookup1 ->Lookup2 ->OLE DB destination(SQL server DB table)

Lookup1 and Lookup2 have error redirected to one flat file destination each.

Thanks in advance!

Geez....the error was just because I hadn't assigned a Connection Manager to that Flat File destination!! Oops!!!

Package templates

Greetings SSIS friends,

I am currently reading Ralph Kimball's "The Microsoft Data Warehouse Toolkit". In the book it mentions creating template packages to speed up the creation of future packages. In the book they also mention creating solutions and projects.

All sounds fair enough but I am confused a little.

Where should the template package be stored?! I created a Project and renamed the default package as "TemplatePackage". I setup some standard data sources and package variables. Do I now create a new package and place it in the same project? Or should my template package be deleted from the project?!

Hope my questions makes sense.

Package Templates
(http://wiki.sqlis.com/default.aspx/SQLISWiki/PackageTemplates.html)|||

That's brilliant.

Thanks a bunch!

sql

Package crashes without error information

I am creating an SSIS Package to import some data. The package contains a big for each loop with 3 parallel running nested for each loops. The package crashes within the big loop without returning any error information. It starts up the sqldumper and genreates an dump - but does not report any error to the UI (Visual Studio or dtexec). While I am running only one for each loop and disable the others the package executes successfully. Has anyone an idea what might be wrong ? or is the only chance to submit a bug report ?

Thanks
HANNES

If it's crashing the package and generating a dump then a bug report is the way to go. This is something we will want to catch and fix for sure.

Thanks

Donald

Ownership chain question

HI,
MS SQL 7.0 on NT 4 (clustered)
Our developers use Infomaker to create many end-user's reports. They are
used to creating many Stored Proc and many "intermediate" tables instead of
creating "pure" Infomaker Reports. Report's components are often modified
directly on Production database during office hours by thoses developpers.
All of our end-user's reports are going to be rebuilt with Crystal Report.
Is it a good idea to ask our developpers to locate thoses end-user's reports
components into another databases instead of mixing DATA and REPORTS
component into the same Production Database ? (I know that we must take care
of Ownership chain)
Thank you
Danny"Danny Presse" <dpresse@.congresmtl.com> wrote in message
news:eA6M9CfXDHA.2476@.tk2msftngp13.phx.gbl...
> HI,
> MS SQL 7.0 on NT 4 (clustered)
> Our developers use Infomaker to create many end-user's reports. They are
> used to creating many Stored Proc and many "intermediate" tables instead
of
> creating "pure" Infomaker Reports. Report's components are often modified
> directly on Production database during office hours by thoses developpers.
> All of our end-user's reports are going to be rebuilt with Crystal Report.
> Is it a good idea to ask our developpers to locate thoses end-user's
reports
> components into another databases instead of mixing DATA and REPORTS
> component into the same Production Database ? (I know that we must take
care
> of Ownership chain)
Yes. Definitely.
Give them guest access only to the production database (you need this for
cross-database views to work).
Create views in their database that proxy over to the production database.
This keeps them from having to bind to the database name of the production
database.
David

override labels for boolean report parameter

I'm trying to override the true/false labels you get when you create a
boolean report parameter. I've tried creating a dataset that I use for my
available values but that didn't work either... Has anyone ever done this or
have any ideas...If you are using the reportviewer you con do that by applying custom language
to it.
look for localysing the report viewer and you will find what you are looking
for.
"Alien2_51" wrote:
> I'm trying to override the true/false labels you get when you create a
> boolean report parameter. I've tried creating a dataset that I use for my
> available values but that didn't work either... Has anyone ever done this or
> have any ideas...