New Forum | Previous | Next | (P-PDF) Developers
Topic: RE: causes of file read errors from avdoc?
Conf: (P-PDF) Developers, Msg: 56637
Date: 5/29/2002 05:20 PM
I don't think it's a problem with the CreateObject call, I'd say it's
related to the processing of the PS file by Distiller. Either create a
sleeper, and wait a reasonable amount of time, or use the Distiller Window
Messages - JobDone message to check that Distiller has processed the file
and released any file locks it may have on the PDF file.
Teryk mentioned a while ago that you can use PDDoc to open your PDF files,
using this Object rather than AVDoc is quicker, since PDDoc doesnt use
Acrobat Dialogs to open files and won't produce any errors if the file is
not found (which would hold processing up for the rest of the files) - it
does however have return codes which you can use to determine if the file
was opened etc.
The reason Distiller is still running even if your app is closed is because
your app still has references to either files, Acrobat or Distiller. Often
Acrobat/Distiller don't clean up properly (through no fault of their own),
so setting the objects to nothing and ensuring that you use the Exit
statement only after you have closed any/all open files should force
Acrobat/Distiller to unload.