At 14:41 06/04/2004 -0300, you wrote:

>Hi,
>
>At April 6, 2004, 12:54, Alexandre Benson Smith wrote:
>
> > Forgot to metion Dialect 1 database.....
>
>This is why IBConsole, IBOConsole and Marathon didn't complain about
>ambiguous fields. I think you've proven that ISQL does a check where
>it shouldn't(on dialect 1 databases), and the bug is more likely in
>ISQL. The ambiguous fields check isn't performed on a dialect 1
>database, but on a dialect 3 database. The reason why it is this way
>is so that old applications(using dialect 1) wouldn't be broken.

Hi Daniel,
What I could not understand is, why the client tools (whatever they are)
don't report the error.... Since it's a server side error...

Thank you for the explanation that it's only reported on Dialect 3... I
don't remenber to read it...

I thought ambiguous fields check will broke any old applications. And I was
wondering why don't break my bogus query... :)

>--
>Best regards,
> Daniel Rail
> Senior System Engineer
> ACCRA Group Inc. (www.accra.ca)
> ACCRA Med Software Inc. (www.filopto.com)

Thank you very much !


Alexandre Benson Smith
Development
THOR Software e Comercial Ltda.
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br

----------


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.631 / Virus Database: 404 - Release Date: 17/03/2004


[Non-text portions of this message have been removed]