>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.
Silvio,
My suggestion has nothing to do with how you edit the data. For example;
USE Customer IN 0 ALIAS Cust1
USE Customer IN 0 ALIAS Cust2
USE Customer IN 0 ALIAS Cust3
SELECT Cust1
SET KEY or SET FILTER to restrict the records in Cust1
SELECT Cust2
SET KEY or SET FILTER to restrict the records in Cust2
SELECT Cust3
SET KEY or SET FILTER to restrict the records in Cust3
Now set the recordsource for grid1 to Cust1, grid2 to Cust2, and grid3 to Cust3. All of them can updatable and refreshing the other grids after a data change will show the change in the other grids.
