David,

Appreciate the fast come back. I took a look at your site and tried a few things but still can't get it to work. Again I have no problems using two tables especially when one of them is the initial selected alias but using three wheer the second parent is the child of the initial selected alias is defeating me. I have tried concatenated fields with and without alltrims and still can't seem to get anywhere. I suppose I could try an updatable parametrized view but I will probably try that last.

>Bruce,
>
>On my website is a simple little example form showing the grid using it's relational settings. And the same grid using a parameterized view.
>
>FWIW you should look at using a parameterized view of the child table it does make the grid easier to work with.
>
>>Okay. This is my first time into table relations for grids using three tables and I am confused. I have an Order Table, an Order Job table and an order line table. One order can have many jobs and one job can have many lines. I have the order header on a form and then a grid showing all the jobs for that order and then a grip showing all lines for a job in that order. All the jobs are showing up okay but I can't get the lines up.
>>
>>The order table is indexed on order number
>>The Job table is indexed on job number and ordernumber+jobnumber
>>The lines table is indexed on ordernumber, Ordernumber+jobnumber, ordernumber+jobnumber+linenumber
>>
>>I have a relation into the job table from the order table on order number.
>>
>>If I set a relation into the item table from the order table using order number then all the lines for that order show up. What I can't figure out is what relation to set into the line table from the job table to limit the lines to the specific job selected in the jobs grid. What obvious (or unobvious) solution am I missing. Thanks in advance.