I know that this error is because of antivirus file locking but is there a way to gracefully deal with this like retrying inside the query.  It's clear that the temporary file was created but can't then be open exclusively to fill.  So it's not that the file does not exist.  My client is using webroot on 100 computers and I'm doing about 100,000 queries a day on each.  And of course odds are that every few days this happens once somewhere.  And webroot won't let you exclude a directory.  And I really don't want to have to check for an exception on EVERY query.  I prefer to assume that they will at least function as designed.   Also you've known about this for a long time and so maybe someone has come up with a clever change to your code that helps?  I'd love to not have to tell my clients to turn off real time scan in any (or some) of it's forms.  Having it helps them to sleep at night.  

George,

<< I know that this error is because of antivirus file locking but is there
a way to gracefully deal with this like retrying inside the query.  It's
clear that the temporary file was created but can't then be open exclusively
to fill.  So it's not that the file does not exist.  My client is using
webroot on 100 computers and I'm doing about 100,000 queries a day on each.
And of course odds are that every few days this happens once somewhere.  And
webroot won't let you exclude a directory.  And I really don't want to have
to check for an exception on EVERY query.  I prefer to assume that they will
at least function as designed.   Also you've known about this for a long
time and so maybe someone has come up with a clever change to your code that
helps?  I'd love to not have to tell my clients to turn off real time scan
in any (or some) of it's forms.  Having it helps them to sleep at night. >>

What version of DBISAM are you using ?  This was fixed a few versions ago -
any time DBISAM creates a temporary file for use with table alterations,
etc. it doesn't close the file anymore in-between the creation and usage, so
you shouldn't be seeing this issue anymore.

Tim Young
Elevate Software
www.elevatesoft.com