D
Dooza
Hi there,
I am using an ASP page to output to Excel file. Its using this at the
top of the page:
<%
Change HTML header to specify Excel's MIME content type
Response.Buffer = TRUE
Response.ContentType = "application/vnd.ms-excel"
Response.Addheader "Content-Disposition",
"attachment;Filename=Export.xls"
%>
I am using an ADODB command to access a stored procedure in SQL 2000.
This stored procedure takes 5 inputs, and returns 2 recordsets.
The first recordset is always just 1 row, and is displayed in a table.
The second recordset can vary between a 10 rows and 35,000 rows.
On smaller rows it works just fine, but with large numbers of rows the
object is destroyed before it gets displayed. I am assuming its down to
the size, or the server giving up, but it doesn't time out which is what
I would expect to happen.
Is there a limit, or is it a resources issue? Can I set the limit if
there is one? Or is there a better way to do this?
Cheers,
Steve
I am using an ASP page to output to Excel file. Its using this at the
top of the page:
<%
Change HTML header to specify Excel's MIME content type
Response.Buffer = TRUE
Response.ContentType = "application/vnd.ms-excel"
Response.Addheader "Content-Disposition",
"attachment;Filename=Export.xls"
%>
I am using an ADODB command to access a stored procedure in SQL 2000.
This stored procedure takes 5 inputs, and returns 2 recordsets.
The first recordset is always just 1 row, and is displayed in a table.
The second recordset can vary between a 10 rows and 35,000 rows.
On smaller rows it works just fine, but with large numbers of rows the
object is destroyed before it gets displayed. I am assuming its down to
the size, or the server giving up, but it doesn't time out which is what
I would expect to happen.
Is there a limit, or is it a resources issue? Can I set the limit if
there is one? Or is there a better way to do this?
Cheers,
Steve