> One good piece is:
> THROW IBCONSOLE AWAY!
> If you want this interface with Firebird, Get a copy of IBOConsole
> IBConsole was buggy at best but is not recommended for use with

Firebird at

> all.
>
> Second piece of advice - Interclient is also an old Interbase

interface. It

> requires Interserver be installed and running on the server which is

also

> not completely compatible with Firebird. You are advised to use

JBird with

> Firebird.
> Check out www.ibphoenix.com for a list of all this stuf.
> Alan

As for IBConsole, I know what you're getting at, but I don't want to
have to re-register all the databases I've got on this machine. I
also have IBOConsole and it seems to have its own set of bugs. Either
way, I don't think this is the cause of my database unavailable messages.

As for InterClient, I agree that JayBird is a much more elegant
solution. We do have some internal applications that use JayBird.
However, in my testing I've been a little underwhelmed by JayBird's
performance. My applications are not as snappy as when I run with
InterClient. Also, the rolling out of JayBird in place of InterClient
is a logistics problem for us. We have a large set of users who
access our server over the Internet and we encrypt the communications
using an encryption proxy which is designed to encrypt one port at a
time and we have designated the InterServer port number as that port.
If we started some users using JayBird they wouldn't be establishing
encrypted connections :-(

Still, I'm not convinced (but could be wrong) that using InterClient
vs JayBird is the cause of the database unavailable problems.

Mike