Save As PDF
- Issue
- John Vanleeuwe
- PowerBuilder
- Saturday, 22 October 2022 07:06 AM UTC
Hi guys,
using PB2019 R2 ( i know :))
we are having a batch processor executable , that does a whole lot of processing on our clients server. We have been updating some of our clients to our latest version of our software. since this update , we are noticing that our executable has stopped working and dissappeared in the morning , only on these "updated" clients.
we have added a lot of debugging , and we have found out that the latest executed line of code is the one just before the dw_tmp.Saveas function
dw_tmp.Modify("DataWindow.Export.PDF.Method = NativePDF!")
write_logging("just before the save as function")
dw_tmp.SaveAs(ls_file,PDF!,FALSE)
if it was a DLL issue, i would suspect its either always failing and not just after a 12 hour span or os.
This function is a generic function we use throughout our application to save a datawindow into a PDF file.
in the application object /tab PDF export , we have checked both
ALWAYS USE NATIVEPDF! METHOD FOR PDF EXPORT
PACKAGING CUSTOM FONTS IN THE GENERATED PDF FILES
Memory leak could be a cause , but then why always on the same statement ( dw_tmp.saveas) ?
Any idea's as to why this exe is closing itself down please ?
P.S. I havent checked the process manager to see if the .exe is still running there and only the visual gui is gone or not.
TIA
John
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.