>>I have a couple of users that get error 1104, error reading file. Usually this happens on a network station, which tells me that their network connection was lost. The perplexing part is how could the error get logged into the error table if the network were down? Any ideas out there? TIA.
>>
>
>Lots of things can cause this, especially if a large number of files are opened at the same time. Some network clients will 'disconnect' a file prematurely in order to free a connection (seen occasionally with some NT Server versions pre-SP5), or will have the network connections lost because the network's central tracker of network resources (the Browse Master station) forgets about the connection (a known bug in Win95, most comonly encountered in peer-to-peer environment or mixed peer-to-peer and NetWare environments where a Win95 system acts as the network Master Browser). It can also be a result of an intermittent hardware problem, where a connection is broken long enough for some, but not all, network file accesses to time out.
>
>>Marcus.

Thanks for the response Ed, and others. I did some tests and noticed when disconnecting the network share that 38 files were open. I then immediately re-established the connection and found that if the network station attempted to use any of those 38 files, it would get error 1104. However, since the errlog.dbf is not one of those 38 files, it has no problem opening file and saving the error. This leads me to the question, is it worth closing and reopening files to avoid this problem? Is their a performance hit for people with stable networks. Maybe it's possible to try to handle this in my error handling routine? Maybe I should leave it as is and try to convince them that their network is having problems. (always a tough sell) What do you think?