You’re offline. This is a read only version of the page.
GL Detail Report consistently prints an extra page. How do I get rid of it?
*This post is locked for comments
I have the same question (0)Which version of Dynamics, and which format of the GL report?
I tested in V7.0 SP1 and didn't have the problem on the standard format.
That being said, Is the extra page blank, or does it have a header with no detail on the last page? If so, there's a nice explanation of the extra "blank" page on this link:
http://www.crystalreportsbook.com/Crystal_Reports_XI.asp?Page=8_2
I've copied it in here (with thanks to CrystalReportsBook.com):
Forcing a Page Break
It is very common to want groups to appear by themselves. Data in each group is listed separately from the other groups. Forcing page breaks makes data from each group appear on their own pages. The group is used to identify where one report ends and the next one starts. An example is a report that has to be broken apart and distributed to multiple people.
Page breaks can be forced to occur either before or after a section. Unfortunately, each option has the problem of always printing an extra blank page. If you force a page break before a group header, then the first page of the report is blank. If you force a page break after the group footer, then the last page is blank. The way around this is to use one of two built-in functions in the conditional formula: OnFirstRecord or OnLastRecord. By doing a Boolean Not in the formula, it temporarily turns page breaks off for the section. For example, if you wanted to force a page break after the group footer, use the following formula (using Basic syntax) in the New Page After format option: Formula = Not OnLastRecord This formula returns True for every record leading up to the last record. Thus, there is always a page break after the group footer. Once the last record is printed, this formula returns False and the option to force a page break is turned off. The last page will not have a page break printed after it.
Basically, what we do with this type of problem is to notify Dynamics Tech Support that there's a problem with the report and then fix it ourselves by copying the original report into the Usr_Rpts directory, correct the issue, and save the corrected report in the Usr_Rpts directory.
Hope this helps.
Gail J-N
Share
Report
All responses (
Answers (
1,000
