Im using the OnFilterRecord Event on a Paradox Table. Has anyone noticed even though if Filtered=false for the Table, the DBGrid scrolls slower? If I take off the OnFilterRecod event from code,it will go back to normal fast scrolling speed.
Its just weird, when Filtered is set to false it deosn't even goto any line in that event. So why does it become slow? The scrolling is even faster when Filter=true.
So go figure........it should be the other way around. Filtering should make things slower ;-)
Any suggestions are very welcome.
Thanks very much.
Im using a Table with about 30,000 records.And a Intel P3 1gz, with 256mb ram , and gb's of free disk space. The key is using a very large Table.
If you would like to test , try using a very large
Table . Set the Filtered property to false during design time, and add some commented lines to the OnFilterRecord Event(no real code is needed there , its just to make the event exist) . Now compile and run , you should have the same results.