ASP page with SQL Server database

[danshap]

I am hoping someone can help me understand a problem I am having with some of my ASP pages. This may just be a lack of my understanding of how a web browser renders a page.

I have an ASP page that queries a SQL Server database and returns a recordset of about 9800 records. Each record returns 11 fields from the database. I am using ADO to connect to the SQL server. When I return the results, I cycle through the recordset and generate a table that will be displayed in the browser.

The problem I am having is that on some machines, the page generates errors (Internet Explorer errors) regarding the system being low on virtual memory. I am using the default cursor location in my code (I am assuming that it is server side cursors).

I have a feeling this problem is occuring on machines that have lower amounts of physical memory (< 128MB). My development machine has 256 and most of the boxes I usually test on are 128.

Is this a logical conclusion as to what is causing this problem? Is there any way I can prevent the problem from occuring?

If anyone knows of any other resources about this, please let me know.

Thanks!!!

[JoshT]

I think the problem is that IE has trouble rendering a 11 by 9800 table. That's quite a large table. The best solution would be to limit the amount of records shown at once. Try Recordset Paging (there's an example at www.asp101.com). Note that all 9800 records will still be received from your web server from the db, but you'll send a smaller table to the browser.