Some months ago Tim revealed that ElevateDB does not require exclusive
locks on its temporary files.  This has the potential to reduce the
problems caused by anti-virus programs accessing the files.  Can anyone
comment on whether ElevateDB reduces these problems in practice?


Regards,
  Oliver

Oliver,

<< Some months ago Tim revealed that ElevateDB does not require exclusive
locks on its temporary files.  This has the potential to reduce the problems
caused by anti-virus programs accessing the files.  Can anyone comment on
whether ElevateDB reduces these problems in practice? >>

EDB solves this problem by simply creating/opening temporary tables in one
shot and not closing them until its done with them.  DBISAM didn't do this
because it was designed to create the table, close it, and then open it.  I
know it sounds like this would be an easy change to DBISAM, but it actually
isn't due to the way it deals with creation vs. opening.  In EDB, table
creation is totally separate from the act of creating/opening the actual
table files themselves due to the catalog.

--
Tim Young
Elevate Software
www.elevatesoft.com