Jason,

> > I believe that SOMETHING could be gbak.
> >Better yet:
> >"should be gbak"...
>
> You can only advise/strongly suggest the correct way to a client, you
> can't hold their hand all the way.

Copying (backing up via some backup-tool) up a life database
(meaning: that's in use by the server process) can cause database
corruption.

What do you want? Tell them to use gbak or get burned for a
corrupt database because you didn't tell them?

The only process/user having access to the physical data file
is the server process (fbserver) or the user under which this
process runs.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com