Adam,

A> The most serious problem is where the virus scanner places a lock on a
A> part of the database file to 'do its thing'. If this operation occurs
A> at the same time the database engine wishes to modify that part of the
A> database file, the database engine will be locked out by the OS.

how do you place a lock on "a part" of a file? Can you define what "a
part" is?

A> This will cause the database engine to panic and shutdown,
A> disconnecting and rolling back all active connections (for SS)

how can you succeed in locking a file or part of it that has been
open, and exclusively locked, by the Firebird server already?

A> If the virus scanner permits, you should at the very least exclude
A> your database folders from the scanning paths.

Absolutely agreed with this and everything else you said below (not
quoted).

Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================