... and hope that the buffer is flushed on complete lines by the process
that is writing the file. It could get tricky otherwise.
and that one can read a file opend by another process... got that
problem switching from os/2 file servers to nt4 back in the days... NT
ans OS/2 share was read only for the reader but the file was locked in
nt, not in os/2, and the program doing it was bought, some old
datalogger, AAC-2 I think...
havent tried that since then in win, but got the feeling somehow that
an app like word for example locks files "harder" than notepad... not
investigated that, so it might be a problem if he cant control the
source of the file... in vms u can do a backup/ignore=interlock but
the problem with flushing the buffer (as Jon said) is still there.
can you get around that with storing data in a DB instead? then you
can use triggers and other methods (Sp to insert data only stores new
data in other table, when you read it clean it) to tell when new data
arrives too...
thats just ideas... good luck..
//CY