Michael,

Sorry for the delay getting back to this.

For my views that have FK lookup values, I do not link the lookup table in the view at all. The view is a simple parameterized view that gets the child records for the parent table. It includes all child table fields. I use a cbo subclass that builds itself from the lookup table, and it is bound to the view field, using column 2 which is the integer key into the lookup table. The cbo only displays the first column, which is the text value for the lookup.

When I create read-only views for this I join the lookup table to produce "human" readable grids.

>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.
>
>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?
>
>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?