Subject Re: [firebird-support] Re: Unassigned code
Author Helen Borrie
At 10:29 PM 9/12/2005 +0000, you wrote:

> > >What is the solution?
> >
> > 1. Get the right message file (firebird.msg for firebird 1.5,
> > interbase.msg for 1.0), ensuring that the server and message file build
> > numbers match.
> >
> > 2. Make sure the right file is in the right place. Should be in
> > root directory.
> >
> > 3. Remove any mismatching copies of the message file from clients'
> > machines. Tip: if the mismatch is coming from the client then
>chances are
> > that client has the wrong client library as well.
> >
> > ./heLen
> >
>many thanks, Helen, but everything looks "proper" to me:

Yes, the server and the message file are in the proper relative locations.

Because of the problem you're seeing, you should determine whether the file
pointed to is the *correct* message file for that server version. In Linux
there doesn't seem to be any way to find out the build version string; but
in Konqueror or equivalent, inspect the property sheet of both the
executable and the .msg file and determine that their 'Modified' property
is the same date and time.

If they are the same on the server, i.e., OK, then one has to suspect that
the client application, somewhere in its layering, is causing the
problem. Maybe you are using a client interface or binary application that
is wrapped around an older client and enforcing use of a local message file.