1. Aart Onkenhout
  2. PowerBuilder
  3. Friday, 10 December 2021 12:36 PM UTC

Hi,

I searched existing issues for this but was not sure: we have a webservice to generate pdf files using NativePDF! I selected the checkbox in the application object of the webservice to package custom fonts. Unfortunately, this doesn't include the fonts. Is this expected behaviour (that is, isn't this feature supported in webservices) or is it due to 'the custom fonts must be a public or enumerated type'?

We're using PB2019R3.

Regards,

Aart

Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 10 December 2021 13:44 PM UTC
  2. PowerBuilder
  3. # 1

Hi Aart,

I don't know if this is related, but have a look at: https://www.appeon.com/standardsupport/search/view?id=7256

Personally I'm having trouble with Crystal Reports and Lucida Sans fonts. Looks like that's a licensed paid font. There's been periods of time it worked on win7, then didn't work on win10, worked again and now it never works on win10. (just in case you'd be using Lucida).

regards and good luck!

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 10 December 2021 17:31 PM UTC
  2. PowerBuilder
  3. # 2

Hi Aart, With NativePDF the PDF is generated on the client machine (not by the Web service).  So after you DataWindow retrieves the data and then you do SaveAs to PDF it is generated.  The font needs to be installed on every single user's machine.  

Comment
There are no comments made yet.
Aart Onkenhout Accepted Answer Pending Moderation
  1. Saturday, 11 December 2021 12:15 PM UTC
  2. PowerBuilder
  3. # 3

Hi Armeen,

I think I don't understand your answer. The saveas is done within the webservice within IIS. So what does this have to do with 'every single user's machine', there's just the server where my webservice resides.

Comment
  1. Armeen Mazda @Appeon
  2. Saturday, 11 December 2021 15:50 PM UTC
Then you are not using the NativePDF option. That was only added to client side.
  1. Helpful 1
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Saturday, 11 December 2021 16:54 PM UTC
  2. PowerBuilder
  3. # 4

Hi Aart;

   Your statement does not make sense when you say Web Service. The only WS option in PB would be the old .Net 2.0 based WS. In that case, the Application object settings are not used. Then for the new .Net Web API web services, they are not PB but, SnapDevelop (aka C#) and that does not support Native PDF feature.

   Can you explain your use / environment in more detail?

Regards ... Chris

Comment
  1. Chris Pollach @Appeon
  2. Sunday, 12 December 2021 18:36 PM UTC
Hi Armeen ... No problem on the server side (like a DBMS) where a Trigger runs a PB App EXE to produce the PDF. Been doing that for decades. ;-)
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Sunday, 12 December 2021 18:48 PM UTC
Hi Chris, The point I was making is that Appeon did NOT design the NativePDF feature for concurrency or to be used in the obsolete .NET 2.0 Web services. So I am just making sure Aart is not misinformed that this is at own risk and not eligible for tech support. My recommendation would be to test carefully under load unless failure of this app is not big deal.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Sunday, 12 December 2021 19:00 PM UTC
For sure
  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.