We are still not sure if our 1104 / 111 / 13 / 1 / 1705 errors are caused by slight network drops, or pure table lockings... if table lockings, we are not sure if they are caused by our antivirus or server settings.. although we have adjusted both per suggestions on universalthread and have reduced these errors.. but we still have them. But corporate policy will not let us remove antivirus software or change much more than what we have done other than in our own code.

What can we do in our fox code to try to recover from 1104/111/13/1/1705 errors ? Can we put in a longer timeout somehow, so our app will keep trying to save the data to the tables.. and if the tables are still locked it will retry for 30 seconds instead of 8??

what else have others done to minimize these errors?
THANK YOU AGAIN
Seth

>From personal experience - there is no recovery from 1104/5 errors - you have to restart the application.
>
>>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