Print Page | Close Window

Details section overlaps Report Footer

Printed From: Crystal Reports Book
Category: Crystal Reports for Visual Studio 2005 and Newer
Forum Name: Report Design
Forum Discription: The best way to design a report and problems you have encountered
URL: http://www.crystalreportsbook.com/forum/forum_posts.asp?TID=5289
Printed Date: 16 May 2024 at 4:20am


Topic: Details section overlaps Report Footer
Posted By: Zodzetrick
Subject: Details section overlaps Report Footer
Date Posted: 21 Jan 2009 at 1:12pm
Crystal Reports Viewer/Designer in VS 2005 Prof. C#

I have a field which sometimes is large, so it is printed on several pages.

When a field is small, ie. starts and finishes on the same page, then all is OK. I mean, that Details vertical lines and field borders are closed as soon as the last field is fully printed. Report Footer is propely printed after the last Details row.

But when a field occupies several pages then, the Details section is not closed after the last row but extends to a whole page.
So, as a result of this behavior, the Report Footer is printed over the Detail's vertical lines. This is my problem.

I tried the following:
1. Change setting Keep Object Together - does not help.
2. Inserting an extra Group Section - Group Footer was printed over on Details body - overlapped.

To show this problem here are 2 pictures. Please pay attention to the column "Odcinki".

http://www.zgadzaj.pl/temp/KIM_Dobry.jpg - The view with a small field
http://www.zgadzaj.pl/temp/KIM_Usterka.jpg - The view with Details expanded to a whole page

Marek


Replies:
Posted By: lockwelle
Date Posted: 22 Jan 2009 at 6:53am
I don't know if this will work, but try creating a second detail row.  It might need conditional suppession.
 
At least it is worth a try.
 
Hope it helps

Posted By: Zodzetrick
Date Posted: 22 Jan 2009 at 10:40am

Unfortunately not. The second Details section is printed over the primary Details section which is still not closed.

Thank you for trying to help me,
Marek

Posted By: Zodzetrick
Date Posted: 25 Jan 2009 at 6:56am
I've extracted and isolated the report into separate project. The project contains application, dataset, data and the report. This project shows the issue related to extended fields.

The project can be downloaded from this http://www.zgadzaj.pl/temp/KimTest.zip - link - ~120KB

I hope it will help to find the solution.

Regards,
Marek

Posted By: Zodzetrick
Date Posted: 27 Jan 2009 at 4:11am
Lockwelle,
 
At last success - I found the workaround!
 
Big thanks for Joe's suggestion in the MSDN forum:
http://social.msdn.microsoft.com/Forums/en-US/vscrystalreports/thread/77b28835-12aa-4592-bcc8-c2b8dbf49317 - http://social.msdn.microsoft.com/Forums/en-US/vscrystalreports/thread/77b28835-12aa-4592-bcc8-c2b8dbf49317
 
and Ludek's and Trevor's help from Crystal Forum:
https://www.sdn.sap.com/irj/scn/forum?forumID=313 - https://www.sdn.sap.com/irj/scn/forum?forumID=313  

Additional Detail section does not help, but addtional Group sections helps.

I removed all vertical lines from the Detail section and the box surrounding the Detail's section row.
I inserted a new group section which works exactly as the Detail section, so it changes along with Detail section.

I put the vertical lines starting from the GroupHeader section and expanded it across the Details section down to the middle height somewhere inside the GroupFooter. And now I set the line's bottom = 0. It means that it end exactly at the start of the GroupFooter section.
Next, I set the height's of GroupHeader and GroupFooter sections = 0.

The import things are:

  • vertical lines (box'es) cannot start in the PageHeader, they must start at top of GroupHeader
  • vertical lines (box'es) cannot end in the Detail section, they must end at top of GroupFooter

And now, it works as I expected. Here is the http://www.zgadzaj.pl/temp/KIM_OK.pdf - PDF example .

Thanks to your advices, too.

Regards,
Marek

Posted By: lockwelle
Date Posted: 27 Jan 2009 at 7:13am
great!  I will try and remember that vertical lines span (it sounds like) from their starting section to their ending section.  So page header to page footer is bad, but group to group is good.


Print Page | Close Window