John,

After playing with different combinations, I believe I have solved the issue.  In print specifications of the datawindow, the paper size was set to default.  We have always left that as default and never had an issue before.  As an experiment I switched it to Letter 8 1/2 11 in (1) and in combination with checking 'Use Paper Size and Orientation Settings from Print Specifications' on the Data Export tab, this solved the problem and the NativePDF exports are now working correctly.

I am also including a very simple sample srd you can import.  You can do an insert row to add a couple of lines of data.  This srd was created in R2, so you will need to migrate it.  Try leaving paper size as default and you should be able to recreate the problem.

Andy

John,

I did what you suggested and compared PDF prints between the R2 version that works correctly and the R3 version with the issue.

The problem is the left margin, in the R2 version the left margin is .25 which is correct.  In the R3 version the left margin is .4375. So the whole report is being shifted to the right and the the overflow is on a second page.

If I hold the 2 pages together and shift one of them so the print lines up, everything overlays correctly, so it does not look like a font issue.  FYI - I am using embedded fonts.  There are 3 fonts in this report, Arial, Arial Bold and Arial Narrow.

Keep in mind that this worked correctly in older versions of Powerbuilder with Ghostscript and 2019 R2 with NativePDF.

Previews and printout are still working correctly, it is just the export with NativePDF that shifts everything over. I tried this with 3 different printers 2 HP and 1 Cannon and I get the same result with all of them.  Printing OK NativePDF not OK.

The only way I can get the NativePDF export to work correctly is to switch the default printer to 'Microsoft Print to PDF'

Andy

Hi, Andy - 

When NativePDF first became available, we noticed similar behavior between output produced with NativePDF and that produced by GhostScript, which we had been using in prior versions of PB.

Can you still create a PDF using 2019 R2? What we did to determine where the minute differences were was to take printouts of the same page of identical data produced in GhostScript and NativePDF and hold them up to a light source with a page from one version on top of the same page from the other version. We could see if the differences were due to margins, font size, character spacing, etc., or combinations of these and other factors.

I'm curious if you have done something similar and if so, can you categorize the difference(s)? Obviously there is some difference, in order for the output to spill over onto a second page.

If things work OK when switching to a different printer, as you described, it make me wonder if the issue is related to the font(s) that are available to the various printers. Are you seeing this issue with many or all reports/printouts or only a few, select ones? What font(s) do the ones that fail use?

Regards, John

Chris,

All I did was migrate to R3, no other changes.  I will open a support Ticket.

FYI - It behaves like an inkjet printer where the right margin is wider than a laser printer.

Thanks,

Andy

Hi Andy;

  If this worked 100% in R2 and you have not changed your App's code or PDF properties - then please, open a Support Ticket for this issue. Also if you can, please provide a simple test case as well and attach it to the ticket. Many thanks in advance!

Regards ... Chris