1. Konrad Kaltenbach
  2. PowerBuilder
  3. Tuesday, 1 June 2021 12:07 PM UTC

Dear Experts,

using PowerBuilder 2019 R2 Build 2353,

I tried to save the content of a DataWindow in a PDF file.
Page 1 is generated fine.
But from page 2 on it seems that all columns except the last one from pages 1,..., n-1 are printed on page n, cf. attached screen shots.
2nd mistake: Not all columns are underlined.

Here is the relevant source code:

integer li_success
string   ls_path

(...)

dw_DataWindow.Modify("DataWindow.Print.Paper.Size=9") //DIN A4
dw_DataWindow.Modify("DataWindow.Print.Orientation=1") //Landscape
dw_DataWindow.Object.DataWindow.Export.PDF.Method = NativePDF!
dw_DataWindow.Object.DataWindow.Export.PDF.NativePDF.UsePrintSpec = 'Yes'
dw_DataWindow.Object.DataWindow.Zoom = 70

li_success = dw_DataWindow.Saveas( ls_path, PDF!, True )


Thanks in advance for all trials to help me.

Kind regards,
Konrad

Attachments (1)
Accepted Answer
Konrad Kaltenbach Accepted Answer Pending Moderation
  1. Wednesday, 2 June 2021 10:13 AM UTC
  2. PowerBuilder
  3. # Permalink

Text Transparency = 0
on Tab Font of the Properties of the affected DataWindow controls made the problem disappear.

Comment
  1. Armeen Mazda @Appeon
  2. Wednesday, 2 June 2021 14:04 PM UTC
Thanks for sharing the solution!
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 1 June 2021 13:55 PM UTC
  2. PowerBuilder
  3. # 1

Hi Konrad, I can’t imagine what you are doing wrong that would cause this problem so this could be some esoteric bug.  I suggest you open a support ticket and provide test case so we can reproduce the problem.  We won’t be able to help if we can’t reproduce it.

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 1 June 2021 18:42 PM UTC
Hi Konrad;

I would also suggest that you copy the problem DataWindow(s) source to your Test Case PBL. Then open the DWO in the DW Painter and then look for the "Data Pane". In the DP, you can manually add some fictitious data and then save the DWO back to the PBL. In that case, the test data is now part of the DWO source. Then attach the test case PBL to the Support Ticket to allow Appeon to delve into your PDF issue further. The nice thing with this approach is that no DML / SQL / DB Connection / Retrieve / etc is required.

Note that the problem could be in the settings used in the DWO(s) themselves, so supplying the DWO source is really the best for the Support Team.

Regards ... Chris
  1. Helpful
  1. Konrad Kaltenbach
  2. Wednesday, 2 June 2021 10:18 AM UTC
Gentlemen, thanks for your advices! Thankfully I could find the erroneous adjustment I made.

Kind regards, Konrad
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 2 June 2021 15:33 PM UTC
Hi Konrad ... that is great news - thanks for letting us know!
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 1 June 2021 18:22 PM UTC
  2. PowerBuilder
  3. # 2

Hi Konrad;

   I would also suggest for your simple Test Case PB App that you use the same DW object(s) that you are using when you create the PDF. Just copy the DWO(s) into your Test Case PBL first. then edit the DWO(s) in the DW Painter and look for the DATA "pane". In there, you can add some test data manually & save it with your DWO source code in the PBL. Then submit that Test Case to Appeon in a Support Ticket so that we can investigate this issue further. Sometimes, it's not the PDF generation that is the issue - it can be related to the way your DWO(s) are constructed (ie: Settings wise).

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.