> I'm not sure I know what you mean by efficient work. Certainly a
> statement like this looks ugly
>
> update tablea
> set field2 = select field2
> from tableb b
> where pk_field = b.pk_field,
> .....
> set field75 = select field5
> from tableb b
> where pk_field = b.pk_field;
>
>
> but in practice, the whole path and expanded record for tableb are in
> cache, so there's not great performance penalty.

Sure, but if I want use a complex select (for example with aggregate
functions), it can't come from cache ;(

Certainly I can use SP...

eMeL