At 01:12 AM 9/12/2004 +0000, you wrote:

>Hi again,
>We actually use third party components who in turn use IBObjects.
>like IBOConsole, IBOAdmin, InterXPress for Firebird.
>While we can modify our source to make IBObjects optionally
>look at a fbclient.dll we can not modify the other Third Party
>components to do such.
>I just can't see why this needs to be a constant.
>It could be used as a part of a LoadLibrary function instead
>of a Hard-Coded solution.
>
>Just thought I would pose the question.

Sure, I think most of us here using Firebird 1.5 would agree that the
question needs an answer and the problem needs a property-oriented solution
rather than the workarounds that tend to solve part of the problem and
raise others.

It will become crucial with Firebird 2, since you will be able to install
multiple instances of the Firebird server, as well as (theoretically) any
version of InterBase on the same host machine. The demand comes naturally
from the desire of open source developers to deploy installable,
shrink-wrapped software that won't step on anything else the customer may
have running on their systems. Whether we think it's sensible for our
customers to blat multiple installations of what's essential the same thing
into their environments isn't really the issue. We can't stop customers
from doing what customers do...so we do have an important need to be able
to deploy customer-proof software.

Helen