[thelist] BIIIIIG tables - HTML or ASP Limitation?

[Nicole Parrot]

I'm facing similar problems. And it's an IIS limitation not a browser
limitation.
Well, to be certain of what I'm saying, I'd need to have the exact error
message you're getting. If it's "Script Timeout", then it's the same one I'm
getting.
The only way around it that I found so far is to present the data in a paged
format. That way, you don't end up with the full table each time.
I'm sure there are other workarounds, but that one worked for me, so I never
investigated further.
Oh, and  you can also change the scripttimeout value to a very large  number
(Mine is now set at 10 minutes!)

Nicole
----- Original Message -----
From: "Luther, Ron" <Ron.Luther at COMPAQ.com>
> I think this is a "common" problem.  You run an ASP report. It tries to
> bring back a 35,000 record recordset ... and it simply "times out" in the
> user's browser.
> I just shot off my mouth this afternoon theorizing that this is a browser
> limitation trying to render a table with "too many" rows ... and not an
> inherent limitation in using ASP to process a dataset.
> The difference is important to me because, if I'm guessing rightly, I
should
> be able to work some "mime-type" magic, write the ASP recordset to a file
as
> ... say .... Excel or CSV ... and then link to the file and have things
all
> work nicely together.  [All in-house intranet where all my users have IE
and
> MS office.]
> Am I close to the mark? ... or do I need to pick up a case of Tabasco
sauce
> to wash down all the crow I'm gonna have to eat?