>Jeff,
>
>I use paramatarized views for this case; the child view contains all records related to all entries in the Master Table/view. The child view has an index and is related via a SET RELATION. The child view does not have to be queried on every AfterRolColChange, I just refresh the controls. The way I understand it, since the controlsource of the child grid, then, is always in tact, the child grid retains its settings.
>
>Hope this helps.
>
>J
>

Yea, kinda what I was getting at without going into the horrifying details. I have a slightly modified version of the txtbtns button set that is in wizstyle ,I think, that navigates to each parent record and if there is more than one child associated it steps through the children and then skips to the next parent record and so on. It works good for walking through customers and their invoices for example but it seems everyone wants it to behave slightly different. A set properties method is a pain but I have learned to accepted it. :)