>Why am I including more than one table in an updatable view. Welllll, that's an interesting answer to your simple question. Actually, I am only trying to update fields from the master table, and bringing a user friendly description of the foreign keys from the joined tables into the view.
>
>I have heard the rule of thumb concerning one table per updateable view. I just haven't figured out how to apply that rule here, in this context.
>

What you do, Kendall, is create a separate view to display the user-friendly stuff - but the view is readOnly - the SendUpdates is .F. The system we're working on right now has well over a hundred views. (there are only about 60 tables in the system). We'll often have 3 or 4 views in a form, but only one is updateable. The others are used to populate list boxes, combos, grids or other devices to present to the user. Anything they can edit is bound to the updateable view.

I know, it takes a while to figure out how to properly put this stuff all together, and I find myself continually refining the techniques.