Re: reading a opened file
- From: erewhon@xxxxxxxxxx (J French)
- Date: Sun, 25 Sep 2005 09:37:24 +0000 (UTC)
On Sat, 24 Sep 2005 16:38:23 +0100, nowhere@xxxxxxxxxxxxxx wrote:
<snip>
>>Also it is possible that the other App is sensible and closes the file
>>after writes and then reopens it in order to guarantee flushing.
>>We really need to know more about the other App
>It wouldn't need to close the file - just flush the buffers. There
>are functions to do that.
Actually closing and re-opening is a lot safer
- that guarantees that the Directory entry is updated on FAT systems
FlushFileBuffers buffers does not say anything about updating the
directory entry
Under DOS one used to create a duplicate file handle, then close the
duplicate to force a proper (complete) flush.
With sensitive files I pre-extend them substantially, then close them,
that way one is writing to existing parts of the file
- the application programmer then can optionally close and re-open the
file after update(s).
However that is not really relevant, as we do not know how this App is
writing to the file ( and it will be a bit tricky checking that out,
as I'll bet it was not coded by the OP )
.
- References:
- reading a opened file
- From: snide
- Re: reading a opened file
- From: Fufi
- Re: reading a opened file
- From: snide
- Re: reading a opened file
- From: Maarten Wiltink
- Re: reading a opened file
- From: J French
- reading a opened file
- Prev by Date: Re: Exit Edit Box on Form
- Next by Date: Re: Setting audio volume
- Previous by thread: Re: reading a opened file
- Next by thread: Re: reading a opened file
- Index(es):
Relevant Pages
|