Martijn,
thanks for replying.

>> it's the first time I run into the need to raise an exception from a
>> UDF; I have seen that my "raise" (I am using Delphi, BTW) is
>> translated by the server into a message "a fatal exception occurred
>> during the execution of a UDF...", which is not that bad but there's
>> room to improve.
>> I was wondering if there is any way to return a more useful (i.e.
>> detailed) error message. InterBase exceptions are out of question here, am

MT> I right?

MT> Right.

MT> The best way I can think of is returning some kind of error code
MT> and that your procedure will translate that code into something
MT> useful.

Unfortunately, the situation that produces the exception is precisely the fact that a
user is trying to access that particular UDF from *outside* any of my
client applications. :-(
Ciao
--
Nando mailto:nandod@...