Page Header Problem


01-14-2010, 6:53 AM

Hello,

Using version 1.6.1651 (and previous versions) we're setting the master report to hide the pageheader on the first page, using PrintOnFirstPage = false. This works fine on multi-page documents, but when there is only one page this setting seems to be ignored. We thought it might be because the PrintOnLastPage settings was overriding this, but this does not appear to be the case as the page header still appears even when they are both set to false. Can you check this out please - by default we would hope that if PrintOnFirstPage was false it would override PrintOnLastPage=true for single page reports as this would make writing report headers simpler.

Thanks,

Joe

 

Re: Page Header Problem


01-14-2010, 9:28 PM
Hello,
Could you please send us rdlx and rdlx-master of the report and master report?

Sergey Abakumoff
GrapeCity

Re: Page Header Problem


01-18-2010, 3:52 AM
Here you go.

Re: Page Header Problem


01-18-2010, 5:19 AM
Hello,
I've tested the problem with the report you have sent and the page header does not show on the first page in both of multi-page and single-page situations. Can you specify - which component is used to preview the report? Is it Windows Forms Viewer? End-User-Designer? Web-Viewer? Or probably you use the application which exports the report to one of the supported formats and opens the resulting document?

Sergey Abakumoff
GrapeCity

Re: Page Header Problem


01-18-2010, 7:47 AM
It is doing it for the windows and the web viewer - the report I attached had more than one page, which works fine. If you reduce the number of rows in the dataset though as I've done for the attached report then you should see the page header appearing.

Re: Page Header Problem


01-18-2010, 9:40 PM
I understand that in order to get the single-page output, the number of records should be reduced.
I was testing the output using exactly this way and the problem does not appear.
I am looking at this again on another machine, will return with the details shortly.

Sergey Abakumoff
GrapeCity

Re: Page Header Problem


01-18-2010, 10:50 PM
I can't repeat the problem.
The page header content(the textbox which shows the value of "PageHeader" parameter) does not print on the 1st page.
The functionality which makes decision about printing/skipping the page header/footer is not touched for a long time, it is thoroughly tested and should work without problems.
Any further information regarding to the steps that can help to reproduce the issue on our side would be greatly appreciated.



Sergey Abakumoff
GrapeCity

Re: Page Header Problem


01-20-2010, 2:40 AM

I have tried this again and there is still a problem.

Can you confirm that when you run the test2.rdlx file and enter a text value for the page header parameter it then does not appear on the  page when it is only a single page report (ie there are only 4 rows in the dataset)? The master page has the properties for PrintOnFirstPage and PrintOnLastPage set to false, so it should not display any page headers for a one page document. However, it is definitely doing doing so for me - I type in a parameter on running the report and it then appears above the main title. I have attached an image so that you can see that this is the case.

Just for the record I am using version 1.6.151.0. Can you have a look at this again please -

Thanks.


Re: Page Header Problem


01-20-2010, 6:25 AM
Good news! I was able to replicate the problem on my side with build 1.6.1651.0
To summarize, the problem is reproducible with the maintenance builds and is not reproducible with the mainline builds.
I believe that we discussed the difference between mainline and maintenance builds before.
As I mentioned before we are doing the sanity checks and performing the testing of the build which can be considered as the 'release candidate'.
This build will include the fix for the problem.

Sergey Abakumoff
GrapeCity

Re: Page Header Problem


01-20-2010, 6:35 AM

That's good news Sergey - I was beginning for a while to think I might need a sanity check of my own!! Pleased to hear that it's already fixed too.

Joe