>>>>>>Is there an easy way to speed up a grid which displays a filtered table? It is extremely slow, no matter how fast the computer is.
>>>>>Jon,
>>>>>
>>>>>Be sure the filter is fully optimizable
>>>>>
>>>>>Better still use a parameterized view to populate the grid.
>>>>
>>>>The grid works at a tolerable speed... until the first record in the filtered set is reached. At this point, if the user scrolls up using the scroll bar or press the up arrow - anything to try to move before the first record - the computer will just hang for about 20 seconds or so. It seems that just the first record is problematic.
>>>>
>>>>I will check the filters again, just to make sure they can be optimized.
>>>>
>>>>The parameterized view might be a possibility, too, although there would be a lot of parameters in this particular instance.
>>>>
>>>>BTW, I'm doing this in VFP 3.0b if that makes a difference.
>>>
>>>The July '97 FoxPro Advisor article "Faster, Better Grids" is worth reading.
>>>Ed B
>>
>>I use a filtered parameterized view on a grid and the grid is on a user-defined page of a pageframe. The speed is OK... Not even half a second to navigate. .
>
>My grid got really slow when I put combos in it and made the combo.Rowsource a SQL which selects several hundred records from a table of a few thousand, and then changed the keys from numeric to character. Navigation and scrolling as well as loading is very slow. The grid.Recordsource is a parameterized view. The SQL looks like: SELECT thingnum, thing_id, thingfield1, thingfield2, thingdescript,thingorder FROM things INTO CURSOR dummy WHERE thinggroup = cGroupVar ORDER BY thingorder.

Unless I don't know enough about ComboBox, I find comboBox very slow when the records grow to a certain size. I always try to avoid combobox for records that will exceed one hundred. It is worse when you put the combobox into the grid. There was once I put it in grid and on the same day, I removed all comboboxes from my grid. Simple reason, the speed is ridiculously slow!