1. Pradeep Sen
  2. PowerBuilder
  3. Tuesday, 26 November 2019 09:59 AM UTC

Hi there,

I am working with a client that has PB12.6 and he want to write a utility to convert legacy PSR files to PDF (saved as blob in a database table).

I have written a small application that does this using XSLFOP! method. I have it working with PB12.6 and fop-0.20.5 version and jdk14. The PSR file get converted to a PDF.

However the PDF output either doesn't format the whole PSR or truncates multiple pages. Only the first DW of a composite DW is converted. Multiple issues. 

Can anyone please tell me if this method is working properly? If yes, what am I missing? Do I need to get a later version of FOP / JDK? I have also downloaded FOP-2.4 (latest version) but that doesn't work with PB12.6. 

Any help would be greatly appreciated.

Thanks

Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 26 November 2019 12:27 PM UTC
  2. PowerBuilder
  3. # 1

I suggest upgrade PB and use NativePDF to save as PDF ==> No XLSFOP issues. Remember to deploy the Native PDF runtime file(s) with your app.

Personally, I haven't used PB 12.6 with XLSFOP!.

HTH /Michael

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 26 November 2019 18:20 PM UTC
  2. PowerBuilder
  3. # 2

Hi Pradeep;

  FWIW: XLSFOP feature never worked well from day #1 of its implementation in generating a PDF file. I would highly recommend switching over to using the DISTILL! option in PB 12.6. Of course if you do migrate to PB2017 or 2019, then the NativePDF! option is also another great choice (as Michael points out).

HTH

Regards ... Chris

Comment
There are no comments made yet.
Pradeep Sen Accepted Answer Pending Moderation
  1. Tuesday, 26 November 2019 20:26 PM UTC
  2. PowerBuilder
  3. # 3

Thanks Michael and Chris.

The system is currently using the DISTILL! option and this client is gradually trying to move off PB so asking them to upgrade is not an option.

There are multiple documents that mention the XLSFOP option and hence the reason for trying this method. Good to know that it has never worked successfully and now I can stop trying.

Thanks guys.

 

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.