> > 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.

I'm not sure, but I don't think the bug is in ISQL.

If ISQL reports ambiguitythingy (or whatever you write it),
it's most probably an SQL WARNING instead of an error.

Or does ISQL have parsing etc build in?

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com