I’m starting to test the 64bit version on a customer site using v15R5 Client/Seerver in a Windows 10/Citrix environment.
One of the current issues is to print to PDF in 'silent 'mode. Using PDFCreator 1.7.3
Server is already in 64bit for a while and the PDF generation from stored procedures is working fine.
On client in 32bits no problem either, but 64bit version Client fails.
The following commands always set the OK variable to 0. And actually don’t work. Because the following 4D print command shows the PDFCreator save dialog window.
SET PRINT OPTION(“PDFOptions:UseAutosave”;1)
SET PRINT OPTION(“PDFOptions:UseAutosaveDirectory”;1)
SET PRINT OPTION(“PDFOptions:AutosaveFormat”;0) //0=PDF
SET PRINT OPTION(“PDFOptions:AutosaveDirectory”;HFSParentName_ ($pdf_path))
SET PRINT OPTION(“PDFOptions:AutosaveFilename”;FileNameFromPath ($pdf_path))
I also tested with only this setting, but it doesn’t work either.
SET PRINT OPTION(Destination option;3;$pdf_path+".pdf")
Strangely, I cannot reproduce this in a vanilla Windows 10 (under Parallels). There the silent PDF generation is working as expected.
Anyone seen a similar issue and knows the solution?