1. Gbenga Owolabi
  2. PowerBuilder
  3. Wednesday, 29 August 2018 20:19 PM UTC

Since we started using PB 2017 R3 , pdf save has been working perfectly.

This version was subscribed to primarily because of the Native PDF

Suddenly at the moment, it stopped working on the client system.

Windows 7 and 10. 32 and 64bits

dw_1.SaveAs(filepath,PDF!,True) 

 

PB.ini content

[Data Window]
NativePDF_Valid=1

Has anyone experienced this, please help with a solution.

Thank you.

Gbenga Owolabi Accepted Answer Pending Moderation
  1. Thursday, 30 August 2018 00:58 AM UTC
  2. PowerBuilder
  3. # 1

Hello Chris,

Thank you so much for the help and headway.

I was able to resolve the PDF issue by generating and running with fresh PB runtime files.

Best Regards,

Gbenga

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 30 August 2018 01:58 AM UTC
Excellent news!



Sounds like the PB runtime files might have been compromised somehow then. I'm glad that you found your issue.
  1. Helpful
  1. Gbenga Owolabi
  2. Thursday, 30 August 2018 10:57 AM UTC
Thanks to you. Cheers
  1. Helpful
There are no comments made yet.
Gbenga Owolabi Accepted Answer Pending Moderation
  1. Wednesday, 29 August 2018 20:58 PM UTC
  2. PowerBuilder
  3. # 2

Hi Chris,

Thank you for the swift response.

We never subscribed to R2 version and there is no installation of such on any client machine.

Is there a way i can identify the R2 dll files and separate the other Dlls if found.

The same installation and settings had been in place from inception of R3 (31 jul 2018).

 

Thank you.

 

Comment
  1. Chris Pollach @Appeon
  2. Wednesday, 29 August 2018 21:13 PM UTC
Sounds like mismatched runtimes then is not the issue.

The NativePDF feature does write an EMF image file to the client's TEMP work folder. Make sure that they still have write permissions to the temp work folder(s).

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 29 August 2018 20:38 PM UTC
  2. PowerBuilder
  3. # 3

Hi Gbenga;

  FWIW: Make sure that you do not mix any R2 DLLs (PB runtime) with the R3 DLLs as this could create an unstable client App.

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.