The combination of grid and filter is an invitation to this kind of problems.
Workarounds include:
SET KEY should work much faster than a filter.
Use a parameterized view. This gives you the additional advantage (over SET KEY) that it allows you to sort the data with temporary index.
HTH,
Hilmar.
>Hi, All,
>
>I have a database is installed on a server for sharing purpose, the application that accesses the database is installed on numerous workstations connected to the server.
>
>As the database size increases, the performance of the application appears to be much slower. Particularly, one form which has the following relationship:
>>Work--Assignments
> |
> |--Clients
> |--Status
> |--Employees
>
>The Work table has more than 380,000 records, it is displayed in a grid on the form. Work table has a "work_id" field and it is indexed. When I SET ORDER TO work_id, SET FILTER TO WORK_ID = 9601. It takes a long time (10) to refresh the grid, when I scroll through the grid, it frezes periodically.
>So, I set the relation off between Work and Assingments right before I SET ORDER TO and SET FILTER TO as mention above, and restore it after that, the performance improves, but it is still slow.
>
>Does anybody have any idea as to how I can improve the performance by any means?
>
>Dawa
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
