Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved nativepdf doesn't work on customers computer

  1. How-to
0
Votes
Undo
  1. Martin Mueller
    Martin Mueller
  2. PowerBuilder
  3. Friday, 18 September 2020 08:07 AM UTC

Hi all,

 

we have the problem, that pdf export (nativepdf) works fine on our developing machine, but not on customers computer. Which file have I to install on customers computer, so he can use this function too?

thanks in advance

Martin

PBVM190.dll Issue once I run my application .exe o...
XML Parsing with PBDOM
Responses (3)
Martin Mueller
Martin Mueller Accepted Answer Pending Moderation
  1. Monday, 21 September 2020 17:22 PM UTC
  2. PowerBuilder
  3. # 1

Hello Miguel, hello Chris,

thanks for helping.

The problem is solved. The customer didn't have any rights to write into the chosen directory :(

best regards

Martin

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 21 September 2020 19:16 PM UTC
Yes, I mentioned that earlier. Upgrading to newer Appeon PB versions will eliminate the need to write to any temporary file(s). Also, there are new options to build the PDF in memory vs to disk. Food for thought.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 21 September 2020 19:42 PM UTC
Strange Appeon did not describe this particular problem as fixed in: https://docs.appeon.com/pb2019r2/release_bulletin_for_pb/Build-2353-MR-BugFixes.html

(not saying it's not fixed).

regards
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 21 September 2020 20:01 PM UTC
Hi Miguel;

Native PDF used to write to the App's location but if you deployed it to a protected area like "Program Files" the FileWrite would fail. Appeon then changed that to write the work files to the Temp area. Then they introduced the new "SaveNativePDFToBlob" command to get rid of TEMP files altogether. That way for secure information in a PDF, the old temp work files are not even only created - if they, are you don't have to worry about them left on disk anywhere

Regards ... Chris
  1. Helpful
There are no comments made yet.
Martin Mueller
Martin Mueller Accepted Answer Pending Moderation
  1. Sunday, 20 September 2020 09:15 AM UTC
  2. PowerBuilder
  3. # 2

Thanks for your reply Miguel,

yes, we distribute the pbpdf190.dll with our app. We use PB 2019 R2 build2328

best regards

Martin

Comment
Load more comments
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 21 September 2020 16:02 PM UTC
What are you exporting?

A datawindow (with nested reports, with RTE)?

The contents of an RTE control?
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 21 September 2020 16:02 PM UTC
Do you get any error message?
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 21 September 2020 16:16 PM UTC
And here my last wild guess:

Does the user have a default printer configured in his/her windows?

That might be important, but not sure with the new PDF functionality.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 18 September 2020 09:04 AM UTC
  2. PowerBuilder
  3. # 3

Hi,

Have you distributed pbpdf190.dll / pbpdf170.dll (depending on which pb version you are using)?

(In somewhat older Appeon versions, pb would try to write a temporary file to the application's install folder. If that would be in program files, there might be an issue when not running the application as administrator.)

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Sunday, 20 September 2020 14:33 PM UTC
Hi Miguel;

Your comment about older NativePDF drivers writing temporary files could certainly be the issue. Early PB2017 versions also wrote them to locations that could be blocked by the host O/S. This issue has been addressed by PB2017R3 in the latest MRs.

Regards ... Chris
  1. Helpful
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.