Issue with opening PDF file from FilePro

[Boaz Bezborodko]

Kenneth Brody wrote:
> Boaz Bezborodko wrote:
> [...]
>> 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.
>
> Define "available".
>
> You still haven't explained why you feel that is "was not possible" 
> for filePro's OPEN() to succeed.
>
According to the way one set of machines handle it, when Adobe Reader 
tries to open the file or when Windows tries to rename it, it gives an 
error that the file action cannot be taken because another application 
has accessed the file.  But the other when the others try to access the 
file under the exact same circumstances then Adobe gives a file-damaged 
error and the Windows rename seems to be ignored.

On the machines where a file-is-being-accessed error appears FP gives a 
negative number for OPEN().  On the other machines the result is always 
"1" even if the file is being written to by another application (in this 
case PrintWizard).  It seems to me that the first set of machines are 
responding correctly and the second set is not.  FP just seems to be 
giving the status that the OS is returning to it.