Hi Dan,

You appear to have tried most of the obvious stuff but for
some reason PB is still unable to access the UDF... the
potential reasons for this would seem to include:

. it cannot find it the UDF (perhaps looking in wrong
root directory)
. the copy it does find seems to be locked (perhaps
a second process has it opened)
. the UdfAccess option in Firebird.conf is denying
access to the UDF (see comments in Firebird.conf)

No, I do not know any way of getting FB to tell you where it
thinks the root directory exists.

- any helpful messages in Firebird.log ?

- using Process Explorer you can search for open handles,
it may be worth checking (while PB is open and has been
trying to access the UDF) to see if some second exe
has been started by PB (or whatever) that has the DLL
open.

> I have also tried setting the FIREBIRD environment variable.

What version of FB is this?
Is the FIREBIRD environment variable set for the separate
server installation?
What method did you use for setting the variable?

(There is a potential issue wrt environment vars in v1.5 and
before that I can explain if relevant - it seems possible to
me that a variation of that problem could carry over to PB
even in v2, but this only applies if you tried to set the
variable from within the PB environment.)


You also mentioned:

> 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.)

I try to remove these entries - they are not necessary for
the typical server installation (the fall-back to the exe
parent directory works), and they confuse things when you
try to run more than one copy of Firebird (even when just
switching between them).


No more ideas off the top of my head so I hope something
here helps.

--
Geoff Worboys
Telesis Computing