Hi Nadya

Users don't complain unless they've had something faster before. That doesn't mean you should not improve performance.

The scrollbar is unaware of the filter, as is the grid <g>, it only shows the number of records.


>Hi Hilmar,
>
>I confirm, filtered grids are slow. Especially when only few records in a table satisfy the criteria. Say, you have 20000 records. Only 20 are problematic and you want to show them in the grid. It's very sloooooooooow...
>
>Unfortunately, our own framework is not build to support views. I have some ideas how to fix the framework, but users didn't complain (may be they are very patient), so we didn't really looked into any alternative solutions...
>
>I also noticed the problem with ScrollBar and discussed it, but didn't get a responce... Scrollbar doesn't behave correctly. I didn't realize, it might be related with a filter...
>
>>>You're quite right, but the grid is the fastest object i know to display data and combinated with a textbox for search it's a ergonomic way to provide data to users.
>>>
>>>Roman
>>
>>Well, what I mean is that, AFAIK, a) A filtered grid is slow. b) A grid with a parameterized view is fast - unless the parameterized view fetches a lot of data for a specific key value. Which seems to be precisely your problem.
>>
>>One possibility is to show the users all data that start with a certain letter(s) - using this as the view's parameter, or one of the parameters.
>>
>>If the user types only a single letter (or none at all!) and then presses a "Show" button, he will have to put up with a longer loading time. That is, users should type at least one, better two or more, letters, most of the time.
>>
>>Hilmar.