>It has all it's ups and downs. The multi .TABLES operation need a lot of manual coding to run properly, The main problem is to figure out if something fails. The Tableupdate logic is not very nice here. I do the one cursor one target logic on an other problem (simply to many fields for one cursor (-.-) ) - I'm unhappy with it either.
>
If you are faced with non-1:1 multitables again, think about a

Select x.x1, a.x2,  a.fk, Space(LenFieldy1) as Y1, Space(LenFieldy2) as y2 from a

and afterwards in a specific method

Update (this.Alias) set Y1 = Y.Field1, Y2 = Y.Field2 from (this.Alias) Join Y on fk = Y.pk

setting Y to a second cursor if it can be modified in the form, otherwise use the base table as Y.
Works for a lot of scenarios I encounter, especially for role-based models (many persons in different roles in one datarecord)