1. Aart Onkenhout
  2. PowerBuilder
  3. Wednesday, 15 August 2018 19:42 PM UTC

Hi,

When using the new SaveNativePDFToBlob function in PowerBuilder MR3 I noticed an emf-file is written to a subdirectory in, in my case, 'C:\Users\aart.onkenhout\AppData\Local\Temp\~temp' and a log-file to 'C:\Users\aart.onkenhout\AppData\Local\Temp\Log\2018_08' (named daynumber.log, so eg. 15.log). The .emf-file is removed after the datawindow is saved to the blob, the subdirectory that was created for the specific .emf-file isn't deleted. As we have a process that will produce thousands of pdf blobs (and save them to the database) it will leave us with thousands of empty subdirectories. I noticed the log-files weren't deleted at all, so that will produce lots of log-files too.

Shoud I report this as a bug or is this by design?

 

Kind regards,

Aart Onkenhout

flexkids (The Netherlands).

Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 21 August 2018 05:39 AM UTC
  2. PowerBuilder
  3. # 1

I'm confused (nothing new there), but … Didn't I see a webinar last week in which we were told that this new function would avoid having problems with needing exclusive rights on a server to write the temp files somewhere on disk? In other words: I shouldn't write at all to disk at any time, not even "under the hood"?

Maybe that's still coming or should that be in R3 already?

 

regards,

MiguelL

Comment
  1. Armeen Mazda @Appeon
  2. Tuesday, 21 August 2018 05:49 AM UTC
This bug should be resolved in the next MR, but it is only writing to the temp folder so it should be compatible with relatively high security config. Of course, to be certain you would need to confirm with the current R3 build to see if it is compatible with your security config.
  1. Helpful
  1. Miguel Leeuwe
  2. Tuesday, 21 August 2018 08:29 AM UTC
"Only writing to the temp folder", well, thanks for clearing that up Armeen and let me too ignore the fact that that was not what was said in the webinar. (At the webinar it sounded very promising).

So .. would It be possible to make this function "really" not use any file writing at all? I mean, someone with some knowledge about file headers and stuff should be able to do that? It doesn't seem impossible to me.

Thanks, MiguelL

  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 20 August 2018 12:32 PM UTC
  2. PowerBuilder
  3. # 2

I hope the file names won't clash if you have multiple users on the same server.

I also have to wonder, is it faster than the usual SaveAs followed by reading the PDF file into memory?

 

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 16 August 2018 08:36 AM UTC
  2. PowerBuilder
  3. # 3

This should be resolved in the next MR, but please follow-up with support through your support ticket on this.  Thanks.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 15 August 2018 20:42 PM UTC
  2. PowerBuilder
  3. # 4

Hi Arndt;

  Yes, the NativePDF feature still goes through building an EMF image as part of it's processing, even though the end result PDF is saved to memory using the new command.

 I noticed the a abudance of log files in beta testing and did report that to Engineering. Looks like that is still active in R3. 

  Please open a support ticket for these items - especially, the excessive logging aspect. I am not sure if the EMF issue is bypassable based on how the current PDF processing is designed but, let's see how Engineering responds to your ticket.

Regards ... Chris

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.