1. Sivaprakash BKR
  2. PowerBuilder
  3. Tuesday, 25 January 2022 11:12 AM UTC

Hello,

PB 2019 R3, PostgreSQL 11

Need to take print out of Application form to be completed by every students of a course, by printing all relevant details of each students in a separate page.   The details to be printed spans Header, Detail and Footer for each student.  

Paper size is A4
Don't want to move the footer contents to Summary area.
Body part contains Autosize Height columns

Creating group datawindow is not a solution, as it doesn't allow us to print the contents in the footer of the page.

How to show all selected students details in a datawindow and subsequently output it to a pdf file?

Edit:  No of rows in detail band varies for each student.

Happiness Always
BKR Sivaprakash

 

Accepted Answer
René Ullrich Accepted Answer Pending Moderation
  1. Tuesday, 25 January 2022 12:36 PM UTC
  2. PowerBuilder
  3. # Permalink

Here is a very simple example.

Attachments (1)
Comment
  1. Sivaprakash BKR
  2. Wednesday, 26 January 2022 12:07 PM UTC
I've given the solution that I found from your coding in a separate reply. Thanks Rene Ullrich.

This solution didn't work in PB 10.5, where we had our original dw, but WORKS in PB 2019 R3 [if built from scratch].
  1. Helpful
There are no comments made yet.
René Ullrich Accepted Answer Pending Moderation
  1. Wednesday, 26 January 2022 12:14 PM UTC
  2. PowerBuilder
  3. # 1

Strange, because the dw syntax is only simple text. I think there shouldn't be such migration issues.

Comment
  1. Sivaprakash BKR
  2. Monday, 7 February 2022 10:57 AM UTC
Rene Ullrich,

I again created a simple data window as you did in PB 10.5 and then migrated to PB 2019. That sample (simple) data window works in both the versions. Don't know why the already built data window didn't work.

Nevertheless we created the same data window in PB 2019 from scratch and it's working like a charm.
  1. Helpful
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Wednesday, 26 January 2022 12:04 PM UTC
  2. PowerBuilder
  3. # 2

Thanks Rene Ullrich

It works !  but conditions apply.  With your suggestion we tried with our already build datawindow.  It didn't work.  After going through your simple example, we tried various combinations, finally found out that re-building the same dw from scratch is the only way out.  To sumup

1.  Migrating dw from previous version of PB (10.5) to PB 2019 ->  didn't work
2.  Save as, from an existing dw within the same PB version -> didn't work  [ tried in PB 10.5 itself ]
3.  Designing a new DW from scratch in PB 2019 -> works out  [ though we are half way in our design ]

To Check
4.  After designing from scratch, Save as a new name and see whether it works or not

If migration has worked out, we would have saved a good amount of time.  
Similarly, save as.   We faced issues when we tried with 'save as' where there were a lot of fields with 'SLIDE UP' property set.  The new datawindow didn't honor the 'SLIDE UP" property for few random fields.  To only solution is to remove all those fields and redesign the dw.   Don't know whether the same issue exists here too.

Happiness Always
BKR Sivaprakash

Note:  I mark this as resolved, will re-open if there are any issues.

 

Comment
There are no comments made yet.
René Ullrich Accepted Answer Pending Moderation
  1. Tuesday, 25 January 2022 11:34 AM UTC
  2. PowerBuilder
  3. # 3

I think Group datawindow with "New page on Group Brake" should do what you want.

I don't see a problem to have information in the footer with this solution.

Comment
  1. Sivaprakash BKR
  2. Tuesday, 25 January 2022 12:16 PM UTC
Thanks Rene Ullrich,

Footer prints at the last page only, NOT in every page as required.
  1. Helpful
  1. René Ullrich
  2. Tuesday, 25 January 2022 12:29 PM UTC
No, footer should be printed at every page.
  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.