>>>If you have a updateable view based on two tables (or n tables), is there any way to tell/force the order in which the tables are updated?
>>
>>I don't think so. If this is an issue, why not break the information into two or more views and cycle through them in the order you require.
>
>Thanks Larry
>
>That is probably the best way. I was trying to see if I could aviod that. My underlying data structure changed and normalizing forced the spliting up of several tables. If I use two views where I previously use one, I have to (find and) add an additional TABLEUPDATE for each view and have to change the ControlSource of about half the controls on my forms. Pain in the butt but probably no way around it.

Okay, I can see the PITA factor is high. However, why do you need to force the update order? Are there row level rules in place on the child table? Because if you set the appropriate key fields for the view, all tables will be updated when you do the tableupdate.