IBO wasn't able to handle all situations that were messed up before either
and so at times I would make use of stored procedures to iron out the usage
of parameters in statements. Also, it's just generally a good idea to put
complex statements in a stored procedure anyway.

Just another way of making this a non-issue for those who would like to have
some insulation from this issue.

It kind of irritates me they would put a client-impacting feature in a
server configuration file. In my opinion this should be an option on a per
connection basis. If I wan't corrected or compatible with old way I should
have a property at the connection level to control this.

Jason

----- Original Message -----
From: "Eduardo Jedliczka" <eduardo@...>
To: <IBObjects@yahoogroups.com>
Sent: Monday, July 14, 2003 5:34 AM
Subject: Re[7]: [IBO] Possible Bug in Parser: Sub-Selects with Integer and
Date Fields In Firebird


> Finally, Thank so much. (Helen)
>
> We use StringReplace (Delphi function) tho change all ":CodEmpresa" from
> "14", but we at a first moment dislike this soluction, and find a "more
> standard".
>
> For the possible changes in IBO parser (maybe like parameters in IBX) we
> think it´s a very good (and very important ) feature!
>
> One more time: Thanks for attention.
>
> And for all IBO Developers, thanks too.