HI Ricardo;

   Yes, you will still need GhostScript if you create PDF's from the Database Painter. The DB Painter still replies on GhostScript when you perform a Save Rows As from the Result Set pane. Also, the internal PDF feature is not available with .Net Assemblies or Web Services.

   The Internal PDF feature is available for all client based applications. That includes Appeon Web and Appeon Mobile.

Regards ...Chris

it is not required, but it is still an option.   you would need to change the pdf generation type to native to use the built in one.  

Hi Ricardo,

If the DataWindow.Export.PDF.Method is Distill! then it requires to install the GhostScript for Dw Saveas PDF. If selecting the DataWindow.Export.PDF.Method as the NativePDF! then it will use the new PB2017 NativePDF solution and won’t require to install the GhostScript and any other software on the client.

As a suggestion, after you upgrade to the Appeon PowerBuilder 2017, you can manually modify the PDF Method into NativePDF! in DW to perform testing. If you are satisfied with the testing result, then you can use the interface as below to implement the NativePDF solution for all of the DW Saveas PDF thus you don’t need to make many code changes manually.

Add the following node in the [Data Window] section in pb.ini:

NativePDF_Valid=1 // it is 0 by default, and it indicates that it uses the one set in the Datawindow property panel. But if it is set to 1 by the customer dynamically then it uses the NativePDF.

Add the following in the [Data Window] section in pb.ini:

NativePDF_IncludeCustomFont=1 // it is set to 0 by default and it means the fonts are not packed. But if it is set to 1 by the customer dynamically then it means the fonts are packed.

Thanks,

Appeon Support Team