I'm fine with handling that the database cannot be in use during the
installation process, as we use Installshield and GUID's to ensure that if
the software has already been installed on the computer, it must firstly be
removed by the user through Add/Remove Programs, thereby ensuring that they
have to be out of the software at the time of the installation.

Thanks for the info.

Myles

===========================
Myles Wakeham
Director of Engineering
Tech Solutions Inc.
Scottsdale, Arizona USA
Phone (480) 451-7440
Web: www.techsol.org

> -----Original Message-----
> From: Alan McDonald [mailto:alan@...]
> Sent: Monday, December 06, 2004 5:15 PM
> To: firebird-support@yahoogroups.com
> Subject: RE: [firebird-support] Transferring database between Windows
> installations
>
>
> > 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?
> >
> > Myles
>
> You can always copy an fdb file IF and ONLY IF you are sure that you have
> exclusive access to it and the server is not running with the threat of
> someone opoening the file while you are copying it.
> If this FDB file is coming out of an installer and is not overwriting an
> existing fdb file which is in use, then I can't see any problems with
> distributing the file like this.
> I'm just going thru the planning of this myself and it will be tempting to
> do it this way.
> A restore does add the increased security of balking at restoring over an
> existing file though.
> Alan
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>