Re: reading a opened file
- From: erewhon@xxxxxxxxxx (J French)
- Date: Sat, 24 Sep 2005 09:00:47 +0000 (UTC)
On Fri, 23 Sep 2005 21:43:17 +0200, "Maarten Wiltink"
<maarten@xxxxxxxxxxxxxxxxxx> wrote:
>"snide" <nospam@work> wrote in message
>news:43341e86$0$10537$4d4eb98e@xxxxxxxxxxxxxxxxxxxxxx
>
>> In fact I woudn't copy the file while it is in a "transitional" state.
>> the data it contains are not complete, so the copy can't be used.
>> So how to know that the file is opened for writing ?
>Open it with file mode fmShareDenyWrite, see if it works?
Yes, that was my initial thought
- the trouble is, that it will cause the other App to throw an error
if it tries to do its thing
- it might not know how to handle such a situation
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
.
- 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
- reading a opened file
- Prev by Date: Re: Strings in file
- Next by Date: w98 losing resources by assigning font.name in tlistview customdrawsubitem
- Previous by thread: Re: reading a opened file
- Next by thread: Re: reading a opened file
- Index(es):
Relevant Pages
|