1. Guillermo Tamburo
  2. Elevate Discussion
  3. Thursday, 19 January 2023 12:57 PM UTC
Hello,
I have an application that generates reports and when using SaveAs( sPath,PDF!, True) it does not generate the file. On the development machine it 
works, but not on the end users' machines. The application is created in 64bit, on both machines the acrobat is also 64bit.
Can someone tell me if I have to install or copy something else on the user's machine. BP version 2019 R3 - Method : NativePDF! Thanks!

---------------------------------------------------------------------

Buenos días,
tengo un aplicacion que genera reportes y al usar SaveAs( sPath,PDF!, True) no genera el archivo. En la maquina de desarrollo si funciona no asi en las maquinas de los usuarios finales.
La aplicación esta creada en 64bit , en ambas maquinas el acrobat tambien es de 64bit. Alguien puede decirme si tengo que instalar o copiar algo mas en la maquina del usuario.
Version del PB
2019 R3 -
Metodo : NativePDF!

Gracias!

 

Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 2 February 2023 20:35 PM UTC
  2. Elevate Discussion
  3. # 1

Please mark as resolved.

Regards

Comment
There are no comments made yet.
Guillermo Tamburo Accepted Answer Pending Moderation
  1. Friday, 27 January 2023 11:12 AM UTC
  2. Elevate Discussion
  3. # 2

The problem was fixed when I copied pbpdf.dll to the same folder where the application is. Thanks to all for the help.

 

 

El problema se soluciono cuando copie pbpdf.dll a la misma carpeta donde esta la aplicación. Gracias a todos por la ayuda. 

Comment
  1. Chris Pollach @Appeon
  2. Friday, 27 January 2023 14:45 PM UTC
Hi Guillermo;

Thank you for that great feedback .. I am super glad that you resolved this issue on your end! :-)

This is also sometimes a problem with the SaveAs() to Excel (especially XLSX) in "some" environments.

This feature works in DEV but not in PROD unless you copy the "PBDWExcel" DLLs to the App EXE's folder.

I am not sure though why some environments require you to do this but, it solves the runtime problem. Looks like your NativePDF has the same requirement.

The curious thing though is as to "why" you need to do this in only a few systems. Just can't put my finger on this limitation (yet). ;-)

Regards ... Chris
  1. Helpful
There are no comments made yet.
Shannon Axon Accepted Answer Pending Moderation
  1. Thursday, 26 January 2023 17:22 PM UTC
  2. Elevate Discussion
  3. # 3

I have the same problem after the PB 22 latest upgrade. In development environment the save as works but not for the user. I've copied all runtime DLLs i could find. Any other suggestions?

Comment
  1. Miguel Leeuwe
  2. Thursday, 26 January 2023 22:13 PM UTC
What if you copy the folder of your network to your local hard disk and try running it from there?
  1. Helpful
  1. Shannon Axon
  2. Friday, 27 January 2023 14:07 PM UTC
Hi Miguel, i get the same problem locally, unfortunately. So strange... I feel like i'm missing something obvious. You know? Chris, since this is the same setup as we've had for years, i don't think the Windows Policy or AV settings would be a problem. Unless there is something to do with the new version of PB.
  1. Helpful
  1. Shannon Axon
  2. Thursday, 2 February 2023 17:01 PM UTC
Just to add a little more detail to this... I found a different place where the user can save a returned set of data and if I opt to save the returned data to excel, the "save as" is successful. It's only when i opt to save as a PDF that no file is created. Anyone had any experience like this? If I run the app through Powerbuilder, i can generate the pdf in both places.
  1. Helpful
There are no comments made yet.
Guillermo Tamburo Accepted Answer Pending Moderation
  1. Thursday, 19 January 2023 13:32 PM UTC
  2. Elevate Discussion
  3. # 4

Cris / Andreas 

 

Thanks!
Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 19 January 2023 13:25 PM UTC
  2. Elevate Discussion
  3. # 5

Hi Guillermo;

  The native PDF feature deployment requires two PB runtime files - pbpdf.dll

  All the runtime dependencies are detailed in the PB help. There is a file difference between PB 2019 vs PB 2022. So you need to read your PB version help.

FYI: 

https://docs.appeon.com/pb2019/application_techniques/ch35s04.html

https://docs.appeon.com/pb2022/application_techniques/PowerBuilder_runtime_files.html

HTH 

Regards ... Chris

Comment
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Thursday, 19 January 2023 13:20 PM UTC
  2. Elevate Discussion
  3. # 6

Hi.

NativePDF requires pbpdf.dll. It is part of PowerBuilder runtime files. If you are using Text Control then you should deploy Text Control's runtime files. For more details take a look at the following link:

Deploying Applications and Components - - Application Techniques (appeon.com)

If you are using PB Runtime Packager to create an msi for runtime, then be sure to check "NativePDF Support" option.

As you are using an x64 exe, you have to deploy dll's from the appropriate folder that should look like: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.xxxx\x64, where xxxx is the Maintenance Release you are using (example 2728).

If you are using Runtime Packager choose "PowerBuilder 64-bit Components" option. Also choose the appropriate Runtime Version.

Andreas.

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.
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.