>>Because it is necessary to install firebird.msg on the client

> Why? You didn't *say* you were used the embedded server,
> but are you?

Not embedded, just a regular client app wanting to talk to
a server super.

"Why?"... Good question. Because I read that in your book,
page 106. ;-)

> So - we are talking about a client-located message file,
> then?

Yes I was, but only because I thought it was necessary for
a client installation. If I can get by without a client
side version of the message file then I am very happy.

What I am actually trying to do is cut down my client
installation to absolute basics. My app plus whatever
minimal other items I really need. So far it seems that
all I really need is the fbclient.dll file. I dont seem
to really need the message file, the firebird specific
registry entries etc. From memory this was not true of
earlier versions, but seems to be true of FB 1.5.2.

I just ran an app on a completely clean system with just
the app and fbclient.dll in the same directory and was
able to connect and work without problem except...

Despite my previous post it seems that isc_sql_interprete is
still not working in this clean system (talking to an remote
server install). No problem from isc_interprete, but the sql
version still seems to be looking for the message file local
to the application, in the directory under the application.
However I still have a few more things to check through, I done
so much stuffing around with bits that I need to make sure I
have not left something in that should not be there.

--
Geoff Worboys
Telesis Computing