Paul,

To answer your question the line you have commented
out below (as distributed) is NOT commented out and
was not the problem. . I found it! Thanks to some
thoughts from Ann and blind head thrashing on my part.

In olden days, the final "ld" line had to contain
extraneous libraries (e.g. -lcrypt or -lgds if you
used any routines there). No longer SO, adding these
things causes irrevocable panic and SQL error -104
(entry point not found).

So I got one routine to work, then two, then all.

Many thanks to you for trying and to Ann who also
tried and gave me more ideas to try.

So I am giving up on making the classic work (remote
connections will not work - xinetd will not bring up
the daemon and no advice worked) Time to go
SuperServer anyway - it may make more sense for the
app.

Ray


--- Paul Beach <pbeach@...> wrote:

> Whats the setting of:
>
>
> # ----------------------------
> # External Function (UDF) Paths/Directories
> #
> # UdfAccess may be None, Full or Restrict. If you
> choose
> # Restrict, provide ';'-separated trees list, where
> UDF libraries
> # are stored. Relative paths are treated relative to
> RootDirectory entry
> # (see above). Default value 'Restrict UDF' provides
> the same restrictions
> # as in FB 1.0. To specify access to specific trees,
> enum all required
> # paths (for Win32 this may be something like
> 'C:\ExternalFunctions',
> # for unix - '/db/extern;/mnt/extern').
> #
> # NOTE: THE EXTERNAL FUNCTION ENGINE FEATURE COULD
> BE USED TO COMPROMISE
> # THE SERVER/HOST AS WELL AS DATABASE SECURITY!!
> #
> # IT IS STRONGLY RECOMMENDED THAT THIS SETTING BE
> USED TO LIMIT
> # EXTERNAL FUNCTION LOCATIONS! SPECIALLY AVOID
> HAVING
> # COMMON SUBTREES IN UdfAccess & ExternalFileAccess
> !
> #
> # Type: string (special format)
> #
> #UdfAccess = Restrict UDF
>
> in the Firebird conf file?
>
> Paul
>
>

__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/