Subject | isc_interprete, isc_sql_interprete etc |
---|---|
Author | Geoff Worboys |
Post date | 2005-02-12T08:59:35Z |
Hi All,
I had no takers for my earlier complaints about like/starting,
so lets try something different.
What do isc_interprete and isc_sql_interprete actually do?
And on a related note: what does the isc_dpb_lc_messages param
do in the attach database call?
Because it is necessary to install firebird.msg on the client
I had supposed that both of the interpret functions were used
by the fbclient.dll to read message formats directly from this
file.
But then I started looking at the isc_dpb_lc_messages param
with a mind to telling the interpret calls to use a different
file, and now I am confused. In order for this parameter to
have any effect on the client it would need to be extracted
by the client API, but...
AFAICT setting isc_dpb_lc_messages to a different client file
is making no difference at all.
isc_interpret is giving me formatted messages almost regardless
of what I do with firebird.msg - which I take to mean it is
reverting to its own internal messages when it cant find
firebird.msg. Thats OK but makes it hard to see what is going
on.
isc_sql_interprete OTOH seems to be always looking for
firebird.msg in the directory below the application location.
This cant be right, but I cant seem to discover what is
actually going on.
Can anyone help explain?
--
Geoff Worboys
Telesis Computing
I had no takers for my earlier complaints about like/starting,
so lets try something different.
What do isc_interprete and isc_sql_interprete actually do?
And on a related note: what does the isc_dpb_lc_messages param
do in the attach database call?
Because it is necessary to install firebird.msg on the client
I had supposed that both of the interpret functions were used
by the fbclient.dll to read message formats directly from this
file.
But then I started looking at the isc_dpb_lc_messages param
with a mind to telling the interpret calls to use a different
file, and now I am confused. In order for this parameter to
have any effect on the client it would need to be extracted
by the client API, but...
AFAICT setting isc_dpb_lc_messages to a different client file
is making no difference at all.
isc_interpret is giving me formatted messages almost regardless
of what I do with firebird.msg - which I take to mean it is
reverting to its own internal messages when it cant find
firebird.msg. Thats OK but makes it hard to see what is going
on.
isc_sql_interprete OTOH seems to be always looking for
firebird.msg in the directory below the application location.
This cant be right, but I cant seem to discover what is
actually going on.
Can anyone help explain?
--
Geoff Worboys
Telesis Computing