In my form, I only used Cursors (created by SPT), so it might have been be easier than in your case.

>I did form with few grids (parents>child1 by parent row, child2 by child1 row etc.
>on child1 text search I can Find only rows that apered for the parent row.
>
>In this status, I fill the parent grid (record source) by table base on dataenviroment alias and the childs with cursors.
>Now, if I want to serch by child1, so controlsource of the child1 is data environment and control source of the previous parent is cursor.
>Its big work to manipulate it and especially doing it clear to user.
>
>
>>Hi Chaim,
>>
>>>Hi
>>>I have 4 tables paren>child1>child2>child3
>>>
>>>The tables relationship manipulate manually.
>>>
>>>
>>>My client wants to see\select information by grid with text (increment search) in few options- search by parents field or by child1 field etc.
>>>I can do 3 or 4 forms and to put grids in each form.
>>>
>>>I ask if its possible doing it in one form with few grids and option to search and view friendly and efficiently in each grid.
>>>
>>>Big Thanks
>>
>>one possible way could be, to read the mastertable, position the cursor on top and read the 1. childtable filtered by the definitions given by the current mastertable record. this logic has to be repeated to all other childs. Instead of rereading the childs work with 'set filter to'.
>>I used this in a 1:mc:mc form for our reports.
>>grid 1 (left) displays groups.
>>grid 2 (middle) displays the existing variants to the current group in grid 1
>>grid 3 (right) displays the existing outputs to the current variant in grid 2
>>a recordchange in grid 1 drills down the set filters to grid2 and 3
>>a recordchange in grid 2 sets a new filter in grid 3
>>
>>If you need to search for records in 'childgrids' that are actually filtered, then you can offer a searchbox above each grid, to find the corresponding records within the mastertable by using the parent ids of the found records. The followings recreation of 'set filter' might be a bit tricky, though.