Hi Jim

Do you mean working directly with the table instead than with grids? The table has never less than 500,000 records. Wouldn't it be to slow? And how would I avoid conflicts when updating? Or better: if I open the same table with different aliases, each one with a filter (I thought filters and grids didn't mix well) what do I update? The aliased tables or only the underlying table? Will the changes on one grid reflect on the other grids during data entry?

I'll give it a try anyway

Thanks a lot.

>>Open the table three times with differnet alias' one for each grid. You can set different filters on the various work areas.


>A customer needs to put 3 grids on a form. He is using my framework that defaults to p-views behind the grids but has no problems working directly with tables. The grids are all based on the same table, as if there were different kinds of records. The problem is that some records that are shown on one grid could also be shown in another grid and both have to be updatable.
>
>How could it be done to minimize conflicts?