I use filters in child grids (when there is a parent-child relation), and I didn't notice any problem, apart from the speed problem, but only when there are scores of thousands of records. Did you notice any additional problems?

>Hi Hilmar,
>
>I would advocate against SET FILTER for grids. We have them implemented in few applications and it turned to be a nightmare. I do not work for that company anymore (and not working at all :(), but I suspect, the applications still use that methodology and the users are suffering...
>
>>>hi thanks for your reply! how to do a parameterize view in grid? TIA.
>>
>>First, it really isn't necessary to worry about views, unless you have more than 20,000 records in the table (or expect the table to grow to this size, eventually).
>>
>>A view is similar to a query, but the results can be sent back to the original table or tables.
>>
>>To define the view, use the view designer from the database. This is easiest from the Project Manager. Don't forget to define which fields should be updateable, and to make the entire view updatable.
>>
>>Suggested name for views based on tables: View names should start with "lv_" (for "local view"). (A remote view is a view based on an external database system, like Oracle or SQL Server.)
>>
>>To add a parameter, use the corresponding tab in the view designer. Define a variable like this: ?tnClientId (to "filter" data for a specific client), or ?tdDate1 and ?tdDate2 (for a date range) (the parameter starts with a question mark).
>>
>>To use the view in the grid, assign it as if it were a table.
>>
>>If the view is parameterized, you must give values to the variables, before opening the view. Otherwise, the user will be asked for the view parameters! I suggest to use private variables for this purpose.
>>
>>Greetings,
>>
>>Hilmar.