"Brad Pepers" <brad@...> wrote in message
news:20011203221436.GOID11056.priv-edtnes10-hme0.telusplanet.net@there...

>
> I think the problem occurs when you are using a system with an older

Firebird

> installation to connect to a new one. I was using one Linux system that

had

> an older beta version before the ambiguous checking changes and connecting

to

> a remote host that had the RC1 version. Does the error message handling

come

> from the client side interbase.msg file? If so, it wouldn't have the

message

> for the ambiguous column names would it?
>
> When I ran the same select command on the system with RC1, then I got the
> ambiguous column error I would have expected.

That's a good question for Ann: where are the msgs supposed to come from?
For example, I know that the dpb to specify an alternate msg file doesn't
work, although the code is in place in the engine.

Maybe the problem is that the engine complains in an inappropriate way if
the requested message is not found. Strange. I remember it said that the
message couldn't be located in the msg file in such case.

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing