I would rather have ambiguity, than have to rewrite every query in
our apps. It is not a matter of sloppy code. It is a matter of
flexibility.

For example

SELECT A.*, B.* FROM TABLEA A
LEFT OUTER JOIN TABLEB B
ON A.ACCOUNT_NUMBER = B.ACCOUNT_NUMBER
ORDER BY ACCOUNT_NUMBER

is not ambiguous. But RC1 says it is, because RC1 assumes that the
value of ACCOUNT_NUMBER in both tables could be different.

I want my users to be able to write their own report queries, and to
be able sort all their screens by clicking on a column heading, and
to be able to create filter clauses by selecting from a field list
etc etc. RC1 makes this all very tricky and very complicated, and
sometimes impossible.

Why can't RC1 do its best to understand the query, and maybe give a
warning if there is ambiguity, and run it anyway. Leave it up to the
developer to remove ambiguity.

This is IMPORTANT. Is there anyone out there who agrees with me?