Page 1 of 1
Batch converting word to pdf
Posted: Fri Dec 29, 2006 8:29 pm
I am trying to modify the Office Inside example to convert a bunch of Word docs to pdf without much success.
Calling the procedure once with the doc filename and destination filename as parameters works great, but as soon as I call it from a process it fails.
After first run I get a "PDFXC3_Globalinit functions failed" and now the pdf is not saved silently but instead the PdfXchange printer driver save dialog is presented.
What am I doing wrong ?
Posted: Fri Dec 29, 2006 8:52 pm
Late last week we made some changes to the behavior of the PDF-XChange Driver OI handling to correct a problem that sounds very much like yours.
Are you using a version of PDF-XChange Driver downloaded this week? If not I suggest downloading the most current build 110 version and try again.
Posted: Fri Dec 29, 2006 10:43 pm
I have downloaded from the site but even though the version displayed on the download page says v.3.60110 19th Dec, 2006 the installation file is stamped 3.60109.
Which one is correct ?
Posted: Sat Dec 30, 2006 11:38 am
I downloaded the indicated file and checked it. Although the installation file PDFXV3SDKPRO_CW.EXE is stamped 3.60109.0.0, the files contained are stamped 126.96.36.199.
I'll bring this to John's attention.
Posted: Sat Dec 30, 2006 3:55 pm
This means I still have the problem.
Posted: Sun Dec 31, 2006 4:41 pm
Apologies for the confusion - I have updated the build info on the install and uploaded - though all the files remain as they were.
Can I ask also - have you tried our standard demo app's to ensure all is functioning correctly with the installation ?
Posted: Mon Jan 01, 2007 12:54 pm
Yes demo apps work.
I am actually using PxcWOI36.app for testing this.
- Calling the main procedure with inputfile and outputfile as parameter works ok.
- Calling it repeatedly from a process does not work.
I do note that there is an orphaned embed: %PXCDV3PBeforeRunEmbed.
This containt this code:
PXCDRV32:PrintInfo.printerDriver = PXCDRV32.GetPrinterDriver()
If I check in the EmbedEditor it looks like the code is placed correctly before:
START(PrintProc, 32000, PXCDRV32:PrintInfo)
Posted: Mon Jan 01, 2007 1:53 pm
Due to a long-standing glitch in the template handling, all #EMBED() points within #CODE templates appear as Orphans in the embed tree.
Posted: Mon Jan 01, 2007 10:03 pm
OK - noted.
Posted: Tue Jan 02, 2007 6:02 pm
Posted: Mon Jan 08, 2007 7:33 am
Posted: Mon Jan 08, 2007 9:31 am