>>The problem is that on page 4 and page 5 I can no longer use the SET FILTER to filter my records. A double SQL will do the job except that I want to bind the grid to my child inventory table and not the SQL cursor.
>
>I think it will be better if I had a flag field on my main inventory table which will indicate if this item has been splitted into the child inventory table. In this case, I will be able to apply the FILTER directly.
>
>Also, I wanted to avoid the cursor because it won't be refreshed automatically when there is a change in the production line. With a table, the grid will refresh automatically.
>
>Anyway, if someone has some comments, I will be happy to hear about them.
>
>Thanks.

I just submitted an article to Foxpro Advisor discussing grids and SET FILTER. You should avoid this combination. I've built a table with 150,000 records and a filter that picks records from 25%, 50% and 75% of the file. This filter takes 3 minutes for the form to appear on my Pentium 100. If you can, use an index and use the SET KEY command.

Mike Yeawood, Toronto, Ontario Canada (cofounder of the Toronto Foxpro User's group).