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

Perhaps we could get it write the queries whilst it's at it
<g>

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

I have been caught on a number of ocassions by 'leaving out
the flexible bits' and not picking up on them when making
changes later. So anything that forces tidier coding and
complains when I'm updating things is fine by me.

Old systems stay with old versions of libraries and
software. When you start to change to a new base, everthing
should be checked anyway, so the oportunity to review code
in the light of 'new bugs' is more of a help than a
hindrance.

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