At 05:01 PM 6/12/2004 -0700, you wrote:

>I know there has been some discussion about how to use gbak to backup a
>database and then restore it on a target machine, but what if you wish to
>include a FDB file with a single user installer that is run embedded on
>Windows? Will the FDB file copy from one machine to another and just needs
>to be installed as another file on the target machine? Will that work?

Theoretically, yes, as long as you can be sure that the target machine has
the same architecture as the machine that created the database, i.e. a db
created on Win32 is copied to Linux on an ix86 machine. Windows-to-Windows
shouldn't be a problem.

Practically, I would recommend deploying the database as a transportable
gbak file and have your installer invoke gbak, or a Services API
application, on the target machine to create and restore the FDB file. A
new installation should start out with a squeaky-clean database...

./hb