Issue with opening PDF file from FilePro

[Boaz Bezborodko]

Kenneth Brody wrote:
> Boaz Bezborodko wrote:
> [...]
>> While I'm trying to nail this down I will probably try something a 
>> little different.  I'll send two jobs to PW about a second apart and 
>> look for the second one.  When it appears then the first must have 
>> been completed already so it is good to go.
>
> Sounds rather kludgey to me.
>
> 1 - Can you guarantee that jobs are run in serial?  (That is, once job 
> A starts, job B won't start until job A completes.)
>
> 2 - Can you guarantee that the second job won't start first?
>
> If you can guarantee #1, then you can force #2 by not submitting the 
> second job until the output file from the first job exists.
>
> As I said, rather kludgey.
>
Bob told me that I can't guarantee that the two would be run 
sequentially, but he did suggest setting up the print file to generate a 
second PDF file which would then run in the same thread and only be 
processed after the first is completed.  It was a simple process to add 
a line at the end of the existing print file to have PW create a second 
PDF file.  The process then looks for the existence of that second file.

This will work whether or not I have a problem with Windows reporting a 
file available when it shouldn't be.


Boaz