Interwizard
Programmer
I've been working in asp.net for a month or so implementing .net whenever possible as apps at our company come up for upgrade. Part of my move to .net I had hoped to try to loose a little of the prejudices I had built up against grids in my vb days and it seemed that MS wishes the world to use grids when displaying data.
My question is, when dealing with moderately large recordcounts, do many of you use grids and if so, how do you overcome the performance pitfalls? Many of our web apps display thousands of records in a paged format. (50+ records per page). In ASP we did this by prelooping through the recordset to get the result cursor at the current "page" of results. It was clunky, but pretty fast and worked well enough.
Now, in .net - a 6,000-8,000 record strongly typed datset is filled in a matter of seconds, but takes minutes to bind to the grid. Any suggestions? Should I abandon the dream of a simple, fast grid in such projects? I'd love to hear what some of you are doing in these cases..
My question is, when dealing with moderately large recordcounts, do many of you use grids and if so, how do you overcome the performance pitfalls? Many of our web apps display thousands of records in a paged format. (50+ records per page). In ASP we did this by prelooping through the recordset to get the result cursor at the current "page" of results. It was clunky, but pretty fast and worked well enough.
Now, in .net - a 6,000-8,000 record strongly typed datset is filled in a matter of seconds, but takes minutes to bind to the grid. Any suggestions? Should I abandon the dream of a simple, fast grid in such projects? I'd love to hear what some of you are doing in these cases..
