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

? I don't get this completely... You mean he's trying to use the UDF without
your app? So he is also accessing the database without your app? If so,
why bother?


With regards,

Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."