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

Resolved Powerbuilder Native pdf method does not work in runtime

  1. Issue
0
Votes
Undo
  1. Ravi Nath
    Ravi Nath
  2. PowerBuilder
  3. Wednesday, 6 December 2017 21:23 PM UTC

Hi,

 

I have a program where I am trying to save datawindow as PDF using the new new feature in usign NativePDf!

 

a_dw.Modify ("DataWindow.Export.PDF.Method = NativePDF!")
a_dw.Modify ("DataWindow.Export.PDF.NativePDF.CustomOrientation = 0")

a_dw.Modify ("DataWindow.Export.PDF.NativePDF.CustomSize = 5")

a_dw.saveas('c:\somefolder\test.pdf", PDF!, false)

This works fine everytime in development environment but in rutime it creates a blank pdf? 

I have used powerbuilder runtime packager with all option checked to deploy it to 32 bit version. I have also checked  that PBPDF170.dll is there.

I have applied the September patch so the date on the pbpdf170.dll is 09/22/17.

It just does not make sense at this point. I need a quick fix as users are frustrated!!!

 

 

 

  1. Build
Automate PowerBuilder UI application testing
PostURL HTTPS
Responses (1)
René Ullrich
René Ullrich Accepted Answer Pending Moderation
  1. Thursday, 7 December 2017 06:26 AM UTC
  2. PowerBuilder
  3. # 1

The user needs write permission to the applications directory because Powerbuilder generates the file dwPage.emf.

Comment
Load more comments
René Ullrich
  1. René Ullrich
  2. Monday, 11 December 2017 07:23 AM UTC
My last info from Appeon: 15.01.2018

  1. Helpful
Olan Knight
  1. Olan Knight
  2. Monday, 11 December 2017 23:27 PM UTC
I certainly hope that the FIX to this issue involves allowing the user to select the location of the storage solder, both as a property we can code, and from a SAVE FILE AS dialog box.



 



Olan

  1. Helpful
René Ullrich
  1. René Ullrich
  2. Tuesday, 12 December 2017 07:00 AM UTC
Chris Pollach wrote (sadly in wrong thread):



The good news is that this oversight should be corrected in the PB2017R2 (revision #2) where the Native PDF feature will now create the dwPage.emf work file in the target folder where you are trying to build the PDF file. Obviously, the target folder should have write permissions already for the App user. The other enhancement will be the creation of a dwPageN.emf file where when the dwPage.emf already exits when threading multiple PDF requests. That means that the PBVM will create a dwPage1.emf, dwPage2.emf, etc work files as required on the fly.

  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.