On Mon, Jul 4, 2011 at 8:17 AM, Tamas Rudnai wrote= : > But dropping the jokes, what we are trying to point out is that something > is > probably wrong in either the software specs or the implementation if you > try > to display few thousands records for each query. Usually customer does no= t > want to read all these records manually but to do something with the > selected records -- statistics for example or do some further actions, so > all can store the results in temporary db leaving the data on the server > side. And if you really need those records down, then either you need a > page > by page view (good example how Google search displays on your screen), or= a > download facility where you can spend some time to download all records t= o > a > suitable file format, plus you do not need to feed up a datagrid view whi= ch > is probably just as resource hungry as the query itself. > Good idea. It's actually MORE resource hungry. I had to inherit the class and double buffer it to improve rendering performance and that helped a bit= .. --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .