>How can an error File is in use by another user generated from an INSERT INTO command?
>
>This is a line being executed 200 times per day for months and today I found this in the log.

Because this is the first time this situation happened (probably). After a few years of network applications, I think the only sure solution (to not have this error :)) is to lock the dbf when you do an insert and set reprocess to 0.

Of course, this is not so good if another user crashes before unlocking the dbf.

You also can set reprocess to a high value: 10-20 seconds and test the database locking before insert. If the test fails after 20 seconds, it's almost sure that there's an error somewhere. Don't be scared about a value of 20 seconds. As long as the system works fine, it will never take so much.

Vlad