>>>>>Gary, try a parameterized grid for your child1 and child2 records instead of letting the grid handle relationships. That way you can put any data you want in.
>>>>>
>>>>>The asterisks are the same as you will see if you do a Browse with 'set skip on'.
>>>>>
>>>>>HTH
>>>>>Barbara
>>>>
>>>>That sounds great Barbara. What's a
>>>>parameterized grid?
>>>>
>>>>thanks Gary
>>>
>>>ARGHH!! I meant a parameterized VIEW!
>>>
>>>Sorry,
>>>Barbara
>>
>>I hate to sound so stupid but when I click on
>>the first parent table what code would be there
>>to make this happen. Could you give me an example?
>>
>>thanks
>>Gary
>
>First you create a view:

>   Create SQL View as Select field list from table1, table2 where ;
>      table1.keyfield = table2.keyfield and .... order by ... ;
>      into cursor CursorName
>

>
>You then use the resulting cursor as the data source for the grid.

Mark gave you the code for a regular view. A parameterized view simply adds one more clause in the WHERE section which can be updated programmatically

   Create SQL View as Select field list from table1, table2 where ;
      table1.keyfield = table2.keyfield;
 >>>     AND table2.SortField = ?MyVar;    <<<<
      and .... order by ... ;
        into cursor CursorName
>

Then be sure you have MyVar programmatically assigned the child value you want to see. You can re-assign MyVar and requery the view whenever Child1/Child2 change.