I have page that has a table the rows of the table are built from a recordset. The number of rows in the recordset can vary from 0 to a few hundred. Anything below 50 rows seems to load fairly quickly, the test query I am using that returns a little over 250 rows will take about 1.3 seconds to generate the data in the server and 50ish seconds to build the page.
I have tried using
<% while not rs.eof %>
<TR>Table columns from recordset, blah</TR>
<% rs.movenext
wend %>
and
<%
dim sOutput
while not rs.eof
soutput = "<TR>" & Table columns from recordset, blah &"</TR>"
rs.movenext
wend
Response.write soutput %>
neither of which appear to be much faster than the other.
Is there a better way to do this and speed up the browser display stime, there are about 5 columns across the page for each row, of which about 18 rows are displayed in the frame before they become hidden and scroll off the bottom.
Quite puzzled as to why the browser struggles to display the small amount of data. I know one answer would be to page it, but the users would really prefer just to scroll down the entire list of entries in one hit.
Thanks for any help to save my hair.
I have tried using
<% while not rs.eof %>
<TR>Table columns from recordset, blah</TR>
<% rs.movenext
wend %>
and
<%
dim sOutput
while not rs.eof
soutput = "<TR>" & Table columns from recordset, blah &"</TR>"
rs.movenext
wend
Response.write soutput %>
neither of which appear to be much faster than the other.
Is there a better way to do this and speed up the browser display stime, there are about 5 columns across the page for each row, of which about 18 rows are displayed in the frame before they become hidden and scroll off the bottom.
Quite puzzled as to why the browser struggles to display the small amount of data. I know one answer would be to page it, but the users would really prefer just to scroll down the entire list of entries in one hit.
Thanks for any help to save my hair.
