Yeah I just relized all this now that you've pointed it out. The requery() on the comboboxes was what was really getting me. Didnt know you had to Thisform.Combo1.Requery() to refill its internal list.
As for the grids, now I remember the old recordsource problem...it wasn't a VIEW that did it..it was when you said like SELECT blahblah Into Cursor MyCursor - and MyCursor was the RecordSource of the grid..
A few adjustments and some design issues to work out & I think I'll have it band-aided the way I want...
oook I'm awake now...geeeze it's Monday for sure.

>Victor,
>
>Using the Requery() function on a veiw will not cause problems for girds and for combos and lists you need to call the object's requery method after you requery the view. Issuing the SELECT command again will cause problems for a gird, but Requery("MyView") will not. If you are issuing the select again you can;
>
>

>Thisform.Grid.Recordsource = ""
>* Do your select again
>Thisform.Grid RecordSource = "TheViewName"
>

>
>This will prevent the grid from losing its mind.
>
>For combos and lists you don;t need anything fancy except that you MUST call the control's Requery method after you repopulate the view. Combos and list hold an internal list of items that ios filled on load and on the Requery method being executed. Simply changing the rowsource's contents does not cause the control to refill its internal list.
>
>

>SELECT ...
>Thisform.Combo1.Requery()
>

>
>You don't even need to hide these controls.