--- In firebird-support@yahoogroups.com, "Myles Wakeham" <myles@t...>
wrote:

> And if there is a challenge to make an 'idiot proof' application

that uses

> FB 1.5 embedded, where the user will be forced to backup, etc. I'm

up for

> the challenge to write it.

Our application is *almost* idiot proof.

The installation of the application is:

1) Insert the CD
2) Click on the Start button
3) Start working.

We have made a single install file using setup factory, which
installes our application, firebird 1.x, the databasefile and a gbak
wrapper. On XP/2000 firebird is installed as a service - on 9x as -a
startet by the "run" folder in the registry. After installation both
firebird and our application is started.


In order to catch things that the user might be doing wrong, we have
some safety build in:

1) We have made a wrappe around gbak called DSAutobackup. After
running DSAutoback succesfully (which can be scheduled), it will
insert a record in the database. If our application cannot see a
successfully backup for 24 hours the user is notified with a list of
things to try. If it fails for 48 hours we will get a email.

2) Every time our user gets an update to the application, the
installscript will call DSUpdate, which will insert a BLOB in the
database containing the setup.exe file. If the user at some point
installs an old version of the application, it will notice that the
database contains a newer version and automaticly reinstall the new
version from the BLOB. That also stops the problem with client A
running a different version then client B.

3) If the user modifies something in the firebird directory it will be
noticed (we store file checksums of ibserver, interbase.msg,
gdsintl2.dll) and repared.

4) If the user cannot logon (and it is not related to 5) ), the file
isc4.gdb can be restored by a click on a button. Users are managed by
the application not firebird.

5) If the user kicks out the network cable, the application will try
to reconnect automaticly 3 times within 30 seconds. If it still fails,
it will popup a message with things to try before calling us. This is
especially nice on WLAN's with bad signals.

6) Some other things I can't remember right now.

We have customers who have installed our application without ever
needing help from us!

Firebird doesn't need a DBA if the developer does his job.

Brian Vraamark