>Yes, you would have to requery the child view as you navigate in the parent. Views are cheap. In other words, it doesn't matter if you add the view to the DBC. What do you mean by grid reconstruction? Do you mean you put a grid on a form that may have different columns at different times while running the form? If so, that's beside the point of using a view versus SET FILTER.

No, but currently I tried your idea not using view, but executing select sql statement into cursor, which is RowSource for the grid. I made this cursor readable by using it again (in VFP 7.0 I would not need to use this trick), and therefore I have to do:

use in select('curActiveLenders')
select * from Lender where ... into cursor curTemp
use dbf('curTemp') again in 0 && to open it again read-write
index on ...
index on ...

My grid becomes blank at this point :( I probably have to try view instead. It doesn't matter, if I put it in DBC, I believe...

Anyway, the current version uses SET FILTER and since Lender table has only 1000 records, I didn't see perfomance problems. But I'm going to try your suggestion, when I find time.
>All you have to do is requery a parameterized view to show different record sets.