Hi Steve,
>
>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.

Thanks for writing back.

I'm with ya' on the read only view for the user friendly stuff, and the editable bound controls for the updatable view. No problem there.

My form in question is deploying a scenario similar to the idea you describe. I am using a read only view for record navigation in a grid and bound controls are using the updatable view. Both views are parameterized. I requery the updatable view using the PK of the read only view like this;

lcMst_PK=V_MASTERIDPARM.Mst_PK
=requery(THISFORM.icMainViewAlias)

So I should be able to requery the 'new read only' view in a similar manner eh? I'll have to give this a try and see what little framework grimlins await me.<s>

But on the flip side, since my view now works as desired using the sequential join syntax, is there a clear risk or benefit to either approach?

I too, am always interested in refining techniques and appreciate your input.

Kendall