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

Resolved DW SAVE AS

  1. Issue
1
Votes
Undo
  1. Samuel Sanchez
    Samuel Sanchez
  2. PowerBuilder
  3. Thursday, 7 April 2022 22:31 PM UTC

Hello.

 

We have an issue with DW in some machines.

In our project, the is a DW_1.SAVEAS(). it will generate a pdf file, but the issue is that this dosent work in some machines, and in other ones, it those generate. Dw.object.dataexport.method is in NativePDF!

 

My question is, it is DW issues or software instalation in some machines, that it cant generetate pdf from dw.saveas(),

If is an software issue... what could be??

 

Thanks

New WebBrowser: event to know Navigate() is finish...
Illegal data type: coderobject (PB2017 R3)
Responses (5)
David Chamness
David Chamness Accepted Answer Pending Moderation
  1. Thursday, 21 April 2022 23:21 PM UTC
  2. PowerBuilder
  3. # 1

Please disregard.  I am my own worst enemy.  The path for the saveas file was invalid.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 22 April 2022 14:25 PM UTC
No problem David ... I have the same problem quite often too when I have not had enough coffee. ;-)
  1. Helpful
There are no comments made yet.
David Chamness
David Chamness Accepted Answer Pending Moderation
  1. Thursday, 21 April 2022 18:09 PM UTC
  2. PowerBuilder
  3. # 2

I just started having this same problem one PC.  It is a Windows 10 machine running PB 2017 R3 Build 1880.  I replaced the PBPDF170.DLL just in case it was corrupt.  

Comment
David Chamness
  1. David Chamness
  2. Thursday, 21 April 2022 20:19 PM UTC
Here is the code I am using for the save as



THIS.Modify ("DataWindow.Export.PDF.NativePDF.UsePrintSpec = YES")

THIS.Modify ("DataWindow.Export.PDF.Method = NativePDF!")

THIS.Modify ("DataWindow.Export.PDF.NativePDF.PDFStandard = 1")



li_Result = THIS.saveas(is_SaveAsFile, PDF!, FALSE)
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Saturday, 9 April 2022 04:36 AM UTC
  2. PowerBuilder
  3. # 3

Hi, Samuel - 

would you please tell us what version, release and build of PowerBuilder your app was developed in?

We ask for this critical information to help ensure our responses are appropriate and correct for your situation. When you do not respond when asked for this information, it makes it more difficult to provide an answer  

I’m working from memory, but please check if pbpdf170.dll, or pdflib190.dll or pbpdf.dll (which one depends upon the version you are using) is included with the rest of the PB runtime dll’s on the machines where this feature is NOT working, as it is required for this feature to function. 

Regards, John

Comment
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 7 April 2022 23:15 PM UTC
  2. PowerBuilder
  3. # 4

What version of PowerBuilder are you using?

If it has the capability, are you using NativePDF? Or Ghostscript?

If you are using Ghostscript, then is it installed on those devices on which you are having problems?


Later -

Olan

Comment
Samuel Sanchez
  1. Samuel Sanchez
  2. Friday, 8 April 2022 16:04 PM UTC
There is no Ghostscipt installed... is there a guide to install it?
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 8 April 2022 17:03 PM UTC
Samuel, Does your app use NativePDF or GhostScript? Which one? If you are using NativePDF you DO NOT need to install GhostScript.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 7 April 2022 22:54 PM UTC
  2. PowerBuilder
  3. # 5

Hi Samuel;

  I wonder if it might be related to a folder permissions issue?

Regards ... Chris

Comment
Samuel Sanchez
  1. Samuel Sanchez
  2. Friday, 8 April 2022 16:19 PM UTC
Thanks Chris, but is all right with permissions
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 21 April 2022 20:28 PM UTC
Since you are using PB2017, the NativePDF feature in that release wrote a lot of "temporary" files to disk when creating the PDF. Often, these temp files could be blocked by the O/S and/or Anti-virus. The NativePDF feature was later revised in PB 2019Rx to not use TEMP files. I would suggest that you migrate your PDF App(s) to PB2019R3 or PB2021 and try the NativePDF feature from that runtime.

Food for thought.
  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.