At 03:32 PM 15/01/2005 +0000, you wrote:

>Hello,
>
>I'm evaluating the FB 1.5.2 embedded server and IBO with my D7 app.
>If I rename fbembed.dll to something other than gds32.dll, how do I
>tell IBO to use the renamed dll? I'm probably wrong about this, but
>IBO seems to be hard-coded for gds32.dll. Thanks!

Gosh, this has been answered soooooo many times!!

"Out of the box" IBO expects to find a client named gds32.dll somewhere in
the path. It will used the first one it finds in the path.

"Different path" isn't an issue with embedded, since the library *must* be
in the app dir and this is the first place the unqualified library name is
sought, under any circumstances.

If you want IBO to seek a library with a different name, you currently have
two choices:

Method 1 (best)
=============
Grab the unit IB_Session511.pas from your IBO root and use it as a model to
create your own unit, e.g. IB_SessionFBE.pas, so you end up with something
like this:

{
}
{
IB_SESSIONFBE }
{
}


{$INCLUDE IB_Directives.inc}


unit
IB_SessionFBE;

interface

uses
IB_Constants;

implementation

initialization
// Replace the normal value with the alternate client DLL value.
IB_Constants.IB_GDS32 := 'FBEMBED.DLL';

end.

Then, in your DPR file, add IB_SessionFBE to the uses clause, making it the
first item in the clause.

Method 2 (hack)
=============
The alternative method is simply to change the string directly in
IB_Constants.pas. This is not recommended, since it will affect all of
your IBO projects, which isn't necessarily what you want.

-------------------------------------------------
The really easy way, of course, is just to rename fbembed.dll to
gds32.dll. As long as it is in the app dir (where it has to be, to work)
it will be the one that's loaded.

Helen