In general, it's known that daemon processes such as antivirus and backup programs can unexpectedly have the journal file open, and interfere with sqlite. If you're deploying sqlite to enduser's machines, you can't change this.
Absent a real solution, I've hacked my copy to retry failed file open/close/delete operations after a short delay. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
