Losing Top of ASP Page

[Eric Wright]

I cannot find any information about what might cause this error, hope someone
here can help.

I am testing our new servers, windows server 2003 with a SQL Server database.
There is an ASP page that accepts a date range and creates an html table for
display. The result set could range from a few rows to tens of thousands.
When a small record set is created, (something less than 5600-5700 rows) the
page works fine. The banner, headings and navigation bar and resulting data
display just fine. If a larger result set is created, (>5700 rows) the
resulting page that displays is garbled because all of the html from the top
of the source is missing. No banner, headings, nav bar or about the first
several thousand rows of data.
If you view the source, it looks as if the top 20,000+ lines have been
deleted. What is displayed is the html from the middle of my loop that
formats the data into the html display. The data it starts with is about
4700 rows into the result set. (Verified by running the stored procedure in
Query analyzer.)

Where it starts displaying data from is not data specific. If I try
different data ranges, it will start displaying at different places. Where
is starts displaying the html is not always the same either, (from within the
loop of the record set.) If I narrow the date range until it gets less than
5700 rows, the page will display fine.

If the page was getting truncated at the bottom, it might make more sense.

I made a test page that executed the stored procedure with a big date range
and just looped and wrote out data unformated. It ran fine. Displaying a
result set of around 6000 rows.

On our current production server (windows NT), the page works fine.

Any ideas on what could be causing the top of the page to disappear??? Are
there server or IIS settings that could cause this??

Thanks in advance.

 

[Bob Barrows [MVP]]

I cannot find any information about what might cause this error, hope
someone here can help.

I am testing our new servers, windows server 2003 with a SQL Server
database. There is an ASP page that accepts a date range and creates
an html table for display. The result set could range from a few
rows to tens of thousands. When a small record set is created,
(something less than 5600-5700 rows) the page works fine. The
banner, headings and navigation bar and resulting data display just
fine. If a larger result set is created, (>5700 rows)

Patient: Doctor, it hurts when I lift my arm above your shoulder.
Doctor: Well stop lifting your arm above your shoulder!

;-)


Seriously, don't write all these records to a single page. What user is
going to be able to process that many records at a time? Implement a paging
solution so the user only has to look at a subset of the records at a single
time. Search www.aspfaq.com for ideas for paging through data.

Bob Barrows
PS. No, I don't know where this truncation is occurring. It has never
occurred to me to even try and display this much data on a single html page
....

 

[Mark Schupp]

First see bob's comment.
Then try adding a response.flush every 500 or 1000 records.

If that doesn't help:
Are records in a table?
show the code

 

[Eric Wright]

Thanks for your comments. I agree with Bob, I'm just testing a system that I
inherited.

Mark, the response.flush worked like a champ. Thanks!

I'll put the paging ideas in my toolbox for the rewrite, if it ever happens.

Eric