We have a windows XP application that creates multiple PS files on the users Hard drive. After they are created within the application we invoke the Distiller program to combine all of these PS files to 1 PDF. This has always worked in prior version of adobe. We recently migrated to Adobe 8.1.1 professional and this function no longer works. The PS files get written fine. When the distiller trys to create a PDF a message is issued "WARNING EMPTY JOB. NO PDF FILE PRODUCED". I am following all the conventions of the RUNFILEX.PS but with no luck. I can create a PDF from a single PS file. When I try to do the create with multiple PS files with RUNFILEX.PS instructions the warning message is issued. I can find no documentation on how to diagnose this error and adobe has been no help.
***
My issue is that the default behavior of Distiller has changed from having unlimited directory access to having limited directory access. The application I support uses Distiller to create PDFs outside of the limited directory access allowed in 8.1.0. It works fine with 8.0.0.
If I manually run acrodist, I can use the -f flag to create PDFs anywhere, and I can create PDFs in the two limited directories that Distiller 8.1.0 allows.
I need to continue having the functionality to create PDFs where I want from within the application. I am automating Distiller using the ACRODISTXLib object. I can find no documentation on overriding this new default behavior using the ACRODISTXLib object. It has a very limited set of methods and properties.
I have tried launching Distiller with the -f flag and reusing that instance, but ACRODISTXLib creates another instance with the GetObject command.
To recap: I'm automating Distiller using the ACRODISTXLib object in Visual Basic. I need to remove the directory access restriction placed on Distiller in 8.1.0. How do I do that? Again, the code works fine with 8.0.0.
Any suggestions would be greatly appreciated.
***
The SDK describing the change is at http://www.adobe.com/devnet/acrobat/downloads/Acrobat_SDK_readme.php
The only lead I have is to convert the code to run from a command line, which would eliminate significant functionality in the application.