> But seriously...check that the correct firebird.msg file is found first in the path. Old versions of firebird.msg don't know about exceptions created for new versions.
>

I think there is no firebird.msg in the path, since by default
Firebird installation doesn't add it, right? In this case, should be
in the client or the server?

> Note that the fact that it's reporting 0 rather than a 9-digit isc code suggests that you might be using a data access interface that does its own interpretation based on hard-coding from an old message database, and returns 0 when it encounters a code it doesn't recognise...so look for that in your driver (if it is your own application) or in the tool (if it is an old tool app.)
>

In this case, I'm using Borland's DBX Interbase driver, so it could be
a problem.

--
Erick Sasse