Hello John,

I believe the grid is populated when it finds enough matches to fill the number of ros visible on the grid. If there are not enough matches (or the matches are at the end of the table) it has to look at all records, consuming more time. Make sure your filter expression is optimizable for best results..

Bob

>My basic problem is that I need to generate a filtered list of a large-ish database and allow users to search the list. This list should use as much "natural" data as possible.
>
>I'm using a form with a generic grid and setting all the columns at run time based on the table name that was passed as a parameter. Building the columns and getting all the parameters straight seems to work fine. Only generic foxpro object are being used here and nothing truly funky is going on behind the scenes (except some DynamicBackColor settings).
>
>The problem comes when I display the list. Here are my commands:
>
>SELECT &mcAlias
>SET ORDER TO
>SET FILTER TO &mcFilter
>SET ORDER TO &mcOrder
>GOTO TOP
>THISFORM.Grid1.Refresh()
>
>This works wonderfully on large lists. This works very poorly on lists that do not fill the grid. Because we are running over a 10 Base T network, the slowdown is magnified. On a returned list of approximately 250 (out of 20,000), the time is measured in milliseconds (0.061 seconds). On a returned list of 4 (out of 20,000), the time is measured in minutes (2.5 minutes).
>
>Does anyone have a clue as to why this happens?
>
>Thanks.
>
>John.