1. Lloyd McBean
  2. PowerBuilder
  3. Wednesday, 22 November 2023 01:46 AM UTC

I have a datawindow which works perfect until I add a nested dw into this to generate details of line-charges.  I am using the latest PB 2022 R2 Build 2828  and nothing I try will get this to stop generating an extra page.

I am out of options.

I have another nested DW in the report, and it prints ok, its in a group header, but when I add a nested DW in the detail band it consistently generates an extra page even if its a single page report.

 

I have tried the following:

1. setting all items in the band to auto-height including the band itself, and numerous other things note in previus posts but nothing stops this behaviour.

2. THIS.Modify ( 'datawindow.PushCutControlToNextPage=yes' ) In the RetrieveStart event of your DW Control

3. Setting all magrins in both master and child DW to 0

Any help to get rid of this behaviour would be greatly appreciated.

Thanks.

 

Lloyd

Lloyd McBean Accepted Answer Pending Moderation
  1. Tuesday, 28 November 2023 03:16 AM UTC
  2. PowerBuilder
  3. # 1

HI Chris.

What I realized is that if I add the nested report (DW child) into a Group Header or Footer, I do not have any extra pages, only when it is added in the Detail band. So what i did was to create a group, and moved the details reporting into the header including the nested report (DW child) and no more extra pages.

It means each row is in its own group, not the most efficient but it solves the problem.  If I need to perform any functions such as click or doubleclick I can always call the BandAtRow function to determine the band and row where the action is triggered and everything else appears to work just fine.

So, question ... is nested reports supported in the Detail band?

 

Lloyd

 

 

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 28 November 2023 19:59 PM UTC
Yes that aspect is supported. If I recall my PowerSoft days correctly ... you can have up to 255 nested DWO's in total in any combination of the parent DWO (including child DWO of a Child DWO, etc). My all time biggest nested DWO was 21 levels of nesting (and it all worked!). ;-)
  1. Helpful
There are no comments made yet.
Lloyd McBean Accepted Answer Pending Moderation
  1. Wednesday, 22 November 2023 18:08 PM UTC
  2. PowerBuilder
  3. # 2

Thanks for the suggestion Chris.

I have searched up and down on main and child(2) DW and cannot find any issue at all.

The only difference here is that the DW that causes this was placed in the Details Band.

Placed report in view mode with margins and found nothing.  Selected all objects and not go over the margins so I am bewildered.

Its causing me pain, any further suggestion could help  -loyal Appeon Developer, HELP!

Is there a way to get a session or paid help to get past this ?

Thanks.

Comment
  1. Chris Pollach @Appeon
  2. Wednesday, 22 November 2023 18:17 PM UTC
Hi Llyod;

If you can provide Appeon with the Parent DWO and the Child DWO's that you are using and a detailed description of how to recreate the issue that you are having ... I would then suggest opening a Support Ticket for this issue. It "might" be a bug - you never know.

Alternatively, if you could provide a simple Test Case PB App instead for the ticket - then that would be even better. If this Test Case demonstrates the exact problem then we can have Engineering trace the issue in the C++ code. HTH

Regards ... Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 22 November 2023 02:39 AM UTC
  2. PowerBuilder
  3. # 3

Hi Lloyd;

  Sounds like maybe an object that exists / extends just outside the page margins. If so, that would then create that extra blank page.  HTH

Regards... Chris 

Comment
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.