At 12:03 PM 7/12/2004 +1100, you wrote:

> > You would have to write the application so that it disconnects from the
> > database before invoking the Execute method of the
> > IBOAdminBackupService. This is probably contrary to the way you usually
>
>???? you mean the IBBackupService? (IBX)

Beg pardon, I meant IBOBackupService. It's in the IBOAdmin suite - it's
like the IBX Admin components but uses the IBO connectivity
framework. Download from www.mengoni.it (or link through from the
Contributed page of the IBO website).

> > write applications for multi-user use. Mostly, we combine the startup of
> > our IBO database apps with the database connection, i.e. we tie the
> > creation of the main form to the activation of the db connection. Though
> > its' what most of us do most of the time, it's not necessarily
> > the best way
> > to implement connections if you want to write scalable apps. It doesn't
> > make sense for multi-tier, for example. Admin tools like
> > IBExpert, et al.,
> > don't do it, of course, since they have no way at startup to know what
> > database they are going to connect to.
>
>I'm yet to find out what IBExpert is actually doing here since I can backup
>a local database but gbak is not present on my PC...

That's because IBExpert uses IBBackupService, which runs the backup
routines via macro calls through the Services API - as does
IBOBackupService. Gbak does too, in its own way - its embedded (i.e. ESQL)
code executes the same routines as the macro that is being accessed by the
Services API.

./hb