- Daniel Vivier
- PowerBuilder
- Tuesday, 14 November 2017 09:37 PM UTC
We just released a new version of our program that includes saving DataWindows to PDF using the new NativePDF feature. It has been working fine for us in testing, but a number of users are reporting getting error messages that indicate that the dw.SaveAs(filename, PDF!, FALSE) method returned -1 (failure).
We definitely included pbpdf170.dll in the installer, putting it into the program's application directory along with the other PB dlls.
Any ideas why this might be happening? We don't know yet whether it is all users or just some users.
We do know that the filename it is saving to is valid - it was selected with a File Save dialog box that wouldn't allow invalid paths.
Is there any debugging possible - further information from the NativePDF functionality about what the problem is?
I'd hate to have to quickly just turn this feature back off! (We do install a separate PDF printer driver with the app anyways, for use in other situations that the NativePDF stuff can't handle, so it fortunately wouldn't be a big deal to turn it off.)
Thanks.
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.