Ann W. Harrison wrote:

> At 05:50 PM 12/21/2004, Roman Rokytskyy wrote:
>
>>Though Dmitry has mentioned an info flag, and I have to check this first.
>
> Where? My e-mail program sometimes junks good messages, but I didn't find
> that one even in the trash.

In Roman's original post one of the options was a new flag. Dmitry
suggested other 'flags' might be used instead, and that was knocked
down, but it may well be a short term solution for Roman. Hence he
needed to check it - and then confirmed that it did not fit the bill
because he needs to know WHAT to prepare.

I think that Jim has grasped the problem, and the longer term solution
is a proper flag, so that you know before preparing a statement just
what you need to convert an incoming 'non-firebird literate' statement
into.

It would be nice if people could remove the blinkers, and realise that
there are users in the real world that do not know about Firebird. Most
of what is being talked about here is to do with allowing Firebird to
handle ports from other systems. So 'noise' about your SQL being the
problem is irrelevant and does not help the discussion. *I* know the SQL
is wrong, but when I change it, I have to make sure that it still works
in all the other engines that are using it as well. Just bodging it to
get the Firebird port working is simply not an option!

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services