Very Computer

We have an update statements similiar to this in several stored
procedures:

Update  FU
set ....
from FU a, BAR b
where a.colname = b.colname

These procedures now bomb with the odbc error:
Cannot use the column prefix 'a'.  This must match the object in the
UPDATE clause 'FU'.

Will 7.0 not allow this style update/join or is there a switch that can
be turned on to allow these ?

Thanks for any help,
Bill

Sounds like an ANSI compatibility thing.  You might want to consider setting
the database to 6.5 compatibility mode.

You don't show the SET clause, but if the SET clause is something like:

SET a.column1 = ...,
         a.column2 = ...

You will get the message you describe. All you need to do is remove the a.
prefix and it will work.

As an explanation, you can only update a single table in an UPDATE
statement, namely the table listed after the keyword UPDATE. Therefore the
columns listed in the SET clause MUST of necessity belong to that table. The
prefix is therefore unnecessary.