This may sound a little naive but we need to intercept / handle all
possible Interbase connection problems. For example the database may
not be visible because a network server is down, the path or name is
invalid or maybe the Interbase server is not running. Very quickly
you can build up a suite of scenarios that can prevent / break an
Interbase connection. It is also evident that this must be a generic
problem and that there must be a generic solution. At the moment,
depending on the cause of the problem, we get a range of odd errors
including lots of undocumented Windows error codes. For our
requirement, the end user needs to receive a very concise and
comprehensible explanation of the problem. So, are you aware of any
source code out there that will avoid us 're-inventing' the wheel
with regard to this problem ?