I agree that, in general filtered grids have their problems but... I want to try to not have to rewrite a huge application. These grids derive fom classes used for filtering and incremental searches according to various indexes, throughout the system - in short this will be a heavy rewrite.

It seems that the problem arises with the interaction between the grid, rushmore, and the data refreshing. When setting set refresh to 0,0 the problem disappeared. Also it seems to be happening more often on fast machines than in slower machines.
Right now I disabled the refresh and setting only when I really need updated data. This seems to make things much better.
Seeting the optimize property to .f. solves the problem, but also slows down the system, especially on slow networks,

Maybe there is another way to get around this bug? A very small delay when refreshing the buffers, if this can be done?

Eylon















>Filtered grids are bad. Not only can you have issues like you're seeing here, but the Ux is not good. The scroll thumb works erratically and not how the user would expect. This causes frustration for the user.
>
>A better option is to only SELECT the data actually needed to fill the grid.
>
>
>>Hello all,
>>
>>Lately we noticed that in certain cases vfp crashes when the grid optimize propert is set to .t.. This seems to happen erraticaly, but usually when opening filtered grids. I noticed that if I set refresh to 0,0 this doesn't happen. I also noticed it happens more often on fast computers than on slow ones. The crash comes with the C00000005 code.
>>
>>Any help would be greatly appreciated.
>>
>>Eylon