1) I'm invoking "DoEvents" within the event (after writing to Winsock--
apparantly this is necessary for the data to be sent) but I'm not having
re-entrancy problems since Timers aren't re-entrant.

2) Sometimes (but not often) I may "Kill" a file and then immediately
"Name" another file to the deleted file name.  I thought maybe there was a
conflict with the OS falling behind  but a simple test project didn't
reveal any problems here.  Maybe the difference is a busy file system? (as
in the case of the machine where the errors are occurring)

3) I am referring to the file by its full path.

4) My only file operations in the event are Dir, Kill, Name, Open (for
Input), Line Input, and Close

5) Just for background, the Timer event is being used as a file watcher.  
Another application writes data to a file and when I see it I read it in.  
Could the other app's access to the file (Append) cause this error?  Some
simple tests tell me no, but maybe other conditions exist.

Thanks for any help,
Joel Moore

I'm using VB5 SP3 on WinNT 4.0 SP3.

Thanks,
Joel Moore

As far as I know this error means the file is not there. And I susspect that
the app that is appending to the file is actually reading its contents,
killing the file, and creating a new file with that name with the data it
wants to save in it. When your app gets this error it is just reading that
file at the wrong time when the file is being changed and therefore does not
exist. You can have your app wait a second whenever it gets this error and
keep trying again until the file has been writen to the disk again.

Thanks,
Joel Moore