Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Re: Blank page in nested report

  1. Advice
0
Votes
Undo
  1. Sivaprakash BKR
    Sivaprakash BKR
  2. PowerBuilder
  3. Tuesday, 14 May 2019 05:07 AM UTC

Hello,

Using PB 11.5 & SQL Server 2012

1.  Blank page when data in nested report exceeds one page.

 

When the data in nested report spans more than one page, it leaves the starting page [of the nested report data] blank and starts in the next page and finishes in the third page.   Is there any way to suppress this blank page ?

2.  Total in nested report appears only when there is more than sufficient space left.

Total of the value is printed in the summary band inside the nested report.  It didn't print when it spans more than one page.   With fewer values, no issues in printing the total.  I tried increasing the band height, to a higher value, then it's printing. 

 

Is there any way / workaround to solve these issues ?

 

Happiness Always
BKR Sivaprakash

 

  1. PowerBuilder
NetServerEnum
Saving PDF File in Database(Informix) and generati...
Responses (4)
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 16 May 2019 23:22 PM UTC
  2. PowerBuilder
  3. # 1

Another thing to chek is if you get these blank pages in the IDE.
If so, then your DWO is wider than the print area; usually this is because you have too many columns or the columns you do have are spaced out wider than 8".

Olan

 

Comment
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Saturday, 18 May 2019 05:50 AM UTC
No Olan Knight. Everything is within the page width. If the nested report's rows are limited, then everything work fine. Only if the rows of the nested report exceeds one page, it skips to next page, instead of continuing in the current page.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 16 May 2019 15:30 PM UTC
  2. PowerBuilder
  3. # 2

Hi Sivaprakash;

  Here is another trick that I use sometimes that might work in PB 11.x (it does in PB2017) ...

In the RetrieveStart event of your DW Control, try adding ...

 THIS.Modify ( 'datawindow.PushCutControlToNextPage=yes' )

HTH

Regards ... Chris

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 16 May 2019 16:57 PM UTC
Undocumented ... don't tell anyone - LOL!
  1. Helpful
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Saturday, 18 May 2019 05:48 AM UTC
No Chris. It doesn't work.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 21 May 2019 14:24 PM UTC
Bummer ... thought that this would be worth a try though.
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 14 May 2019 15:24 PM UTC
  2. PowerBuilder
  3. # 3

Sivaprakash -

1. Ensure that every object in the ban, INCLUDING the band itself, has the AUTOSIZE HEIGHT property ON.

2. Exit the dw. Regenerate. Reopen the dw to test.

 

Olan

 

Comment
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Wednesday, 15 May 2019 06:50 AM UTC
Thanks Olan,

Did I forgot to add that the issue is at runtime ? Looks like you understood it as a design time issue. Nevertheless I'll try it.
  1. Helpful
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Thursday, 16 May 2019 11:28 AM UTC
The issue remains same, even when all columns and bands have been marked autosizeheight with true.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 14 May 2019 15:17 PM UTC
  2. PowerBuilder
  3. # 4

Hi BKR;

  Unfortunately, there is no longer any support from SAP for Sybase versions of PB. The only thing that I can suggest, is to migrate your App to PB2017R3 or the new PB2019 GA release coming out in a few weeks. Then try your App's nested DW printing on a supported PB version. If the issue still exists, at least you can open a support ticket with Appeon.

Regards ... Chris

Comment
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Wednesday, 15 May 2019 06:50 AM UTC
Yes I know Chris. Unfortunately it will take some more time for me to switch to PB 2017/19. Till then I need to run this in PB 11.5 and solve this issue.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.