> > curious, since when using embedded, you have successfully locked any
> other
> > potential user from getting access to your data file. Why are you
> trying to
> > shut it down?
> > Alan
>
> Thanks again Alan:
>
> I ran IBPP's sample code, test6 is a function that backups and
> recovers a database. Not two operations that naturally fit into one
> function in my oppinion. But the code seems to work, and after the
> call to ServiceFactory the next calls are to Service::Connect() and
> Service::Shutdown().
>
> The backup and recovery functions are part of my firebird_utilities
> library, and should handle any type of server.
>
> However, I really would like to get something working tonight (U.S.
> West Coast) and I'll be happy if you can help me get something going
> that depends on certain advantages offered by the single user nature
> of the embedded server.
>
> I like IBPP, and now that I see IBPP has features that take
> advantage of the service API, I'm interested in pursuing that
> approach. Is this an appropriate forum for discussing IBPP issues?
>
> I'm also attempting non-IBPP Services API code, and I think I'll
> start a sub thread that deals with my attempts to get that going.
>
> Thanks
> Larry
>

no need to shutdown in the embedded environment. No need to disconnect
either so there's no need to connect after backup.
If you want to restore than that's another animal. You'll need to disconnect
from previous (old) file and connect to new one. In a remote setup you may
wish to
I suspect shutdown filas in embedded since security is bypassed in the
embedded and you need to be SYSDBA to shutdown a DB.
Alan