Running software that references a network database, we've been getting into plenty of 1104, 1705 and other file reading/writing errors. We've also been able to reproduce a lot of these errors by (surprise) unplugging the remote computer from the network while it's attempting to read/write to the database. The funny thing, however, is that the errors will be avoided if the connection is re-established within 8 seconds. After 8 seconds, however, a flood of error messages occur. Has anyone found a good coding solution for anticipating and dealing with intermittent network connection? Any thoughts? Thanks

David