Subject | Re: [firebird-support] Determining the Root_Directory |
---|---|
Author | Helen Borrie |
Post date | 2007-12-26T20:41:45Z |
At 05:52 AM 27/12/2007, you wrote:
Your fbembed.dll needs to be renamed to either fbclient.dll or gds32.dll. Are you sure that PB is finding the right library or could it actually be connecting to the *full* server through a regular client (perhaps an InterBase one) in its own search path?
./heLen
>I am starting Embedded Firebird from within PowerBuilder, and it isThat's the full server. If you're running embedded, its search path is different.
>not finding my UDFs.
>
>I have tried putting a Firebird.conf file specifying the
>Root_Directory (under which I have the UDFs in a UDF directory) in
>both the directory in which the PowerBuilder executable lives, and
>the directory where it starts (as set is its shortcut). Also in the
>directory that the ODBC driver is in.
>
>I have also tried setting the FIREBIRD environment variable. I also
>have a Server installed, and a UDF directory under the directory that
>is the DefaultInstance value of the
>HKEY_LOCAL_MACHINE\SOFTWARE\Firebird Project\Firebird
>Server\Instances registry key. (According the Firebird book, those
>are the first two places it looks to determine the Root_Directory.)
>None of this seems to work.Embedded's RootDirectory is the one where fbembed.dll is.
>
>Is there a way that I can interrogate a running Firebird instance
>(whether embedded or server) to ask what it thinks its Root_Directory
>is? That would help me sort this out.
>By the way, when I run my compiled PowerBuilder application (i.e. notThat's how embedded needs to be set up. I don't know how PB establishes its execution paths but, with Delphi, one keeps the (renamed) fbembed.dll in the project's source directory (which is also where the executable is created).
>from within the PowerBuilder IDE), everything works as it should. The
>UDF directory is under the application directory, there is no
>firebird.conf file needed, and it finds the UDFs.
Your fbembed.dll needs to be renamed to either fbclient.dll or gds32.dll. Are you sure that PB is finding the right library or could it actually be connecting to the *full* server through a regular client (perhaps an InterBase one) in its own search path?
./heLen