>How do you guys use only views in these scenarios:
>
>1. a parent table (20000 recs minimum search) with 6 lookup tables displayed in a grid
>
>2. data entry using the above.

Basically, I would not join lookups here, i.e. I would retrieve data from one (master) table only, and use customized column.controlsources to show lookup fields.

>I have users who want to see data when they enter the form( Why, I don't know why?!?!?!) so a PV only works after theyhave been presented with data to allow them to narrow their search. Right now, since we have not converted old data and the test phase has not completed, the grids work fast. I have warned the users that when the converted data gets in and they have to do data entry that their form will be slower than molasses in the North Pole in winter.
>
>QUESTION: I have not tried this myself but would like to know if you have. If you create a view that is updatable and include the lookup fields but don't include them as updatable, don't you have to create a custom save routine to save the key value into the view with REPLACEs?

When you save new foreign key value it still goes to master table. i.e. you shouldn't update lookup tables at all.

>QUESTION: I have not tried this myself but would like to know if you have. If you create a view that is updatable and include the lookup fields and you include them as updatable, won't your lookup tables get updated as well as your base view?
>

Yes, it's possible. The only requirement is that view's primary key should include lookup fields too.