Weird handling of openfiles (was Issue with opening PDF file from FilePro)

Boaz Bezborodko boaz at mirrotek.com
Fri May 29 13:23:32 PDT 2009


Kenneth Brody wrote:
> Boaz Bezborodko wrote:
> [...]
>> I decided to peek into what the different machines showed as the file 
>> status that was returned by OPEN() and found that the machines that 
>> had the problems always returned a 'valid' file handle ('1' ) even 
>> though it was not possible for it to be available from the very 
>> beginning.  The machines that worked gave a negative number until the 
>> file was ready.
>
> If OPEN() returned 1, then the open succeeded.  Why do you believe 
> that it "was not possible" to succeed?
>
>> All are connected to the same server and have almost identical 
>> environment setups.  I'm at a loss in explaining why some machines 
>> are properly reporting the file status while others aren't.  It must 
>> be related to Windows, but I have no idea where to look.
>
> On those where it fails, what error is returned?
>
>> Does anyone have any suggestions?
>
In this case the problem comes up when Adobe attempts to read the file 
and gives an error that the file is damaged.  In addition to the handle 
of the file I also had the program output the size of the file and it 
shows the file as being available even when all the data isn't there.  I 
also confirmed this by trying ot open the file in Adobe as the file was 
being built and once it was done.  So long as all the data wasn't in the 
file Adobe gave me the damaged file error.  Once all the data was in the 
file Adobe could open it without an error.

I pretty sure that this is a problem with some of my Windows 
installations and not an FP problem since Adobe responds differently on 
the computers which give the proper file status response.  When I try to 
open the file on those computers as it is being built Adobe gives me an 
error that it couldn't open the file since it is being used by another 
application.  I get a similar indication when I use Nancy's method of 
renaming the file.  On the machines that behave properly it gives me an 
error that the file cannot be accessed because it is used by another 
application.  But it just goes right along as if the file could be 
renamed on the machines with the problem.

Boaz


More information about the Filepro-list mailing list