I have a table that displays the entirety of our warehouse inventory.



I thought about encapsulating the processing into a component, and then

returning a big string of HTML to the browser, but I found there was a big

performance penalty...  It would work correctly, but take forever to finish

displaying the page.



So I stuck to using ADO in my ASP page to do the processing and display.  I

used the .GetRows(-1) method to speed things up.



I would like to use the component if possible, but is this a situation where

putting that into a component would really not help?

Any advice as to what I should do?  I also set Response.Buffer = False, if

that would make a difference with a component...



Thanks for the advice, o gurus.



Regards,

Arbon Reimer

That is what I do with the large recordset. I use the component that

returns the client side recordset (rs.CursorLocation = adUseClient) to the

asp, and then use the paging method on the asp page which returns, lets

say, 15 records per page (which loads pretty fast) and then user can go to

the next page and so on. One obvious benefit of the client-side cursor is

quick response. After the result set has been downloaded to the client

machine, browsing through the rows is very fast. Because it is a client

side recordset it takes some time initially to load the recordset but then

it's pretty fast loading all the rest of the pages. The paging will make

downloading your html faster and user don't need to wait till it builds the

entire html table with all the records.



Hope this will help,

Victoria...











"Arbon Reimer" <arbon_reimer@h...> on 04/27/2001 01:51:14 PM



Please respond to "ASP components" <asp_components@p...>



To:   "ASP components" <asp_components@p...>

cc:

Subject:  [asp_components] Big Recordset - component or use only ASP?





I have a table that displays the entirety of our warehouse inventory.



I thought about encapsulating the processing into a component, and then

returning a big string of HTML to the browser, but I found there was a big

performance penalty...  It would work correctly, but take forever to finish

displaying the page.



So I stuck to using ADO in my ASP page to do the processing and display.  I

used the .GetRows(-1) method to speed things up.



I would like to use the component if possible, but is this a situation

where

putting that into a component would really not help?

Any advice as to what I should do?  I also set Response.Buffer = False, if

that would make a difference with a component...



Thanks for the advice, o gurus.



Regards,

Arbon Reimer

does it have to be everything on one page or could you maybe display 25

records on a page and have an optional search engine?



Jonothon Ortiz

Senior Web Developer

Xnext, Inc.

Ph:  xxx.xxx.xxxx

or  888.84.XNEXT

http://www.Xnext.com

mailto:jon@x...



-----Original Message-----

From: Arbon Reimer [mailto:arbon_reimer@h...]

Sent: Friday, April 27, 2001 1:51 PM

To: ASP components

Subject: [asp_components] Big Recordset - component or use only ASP?





I have a table that displays the entirety of our warehouse inventory.



I thought about encapsulating the processing into a component, and then

returning a big string of HTML to the browser, but I found there was a big

performance penalty...  It would work correctly, but take forever to finish

displaying the page.



So I stuck to using ADO in my ASP page to do the processing and display.  I

used the .GetRows(-1) method to speed things up.



I would like to use the component if possible, but is this a situation where

putting that into a component would really not help?

Any advice as to what I should do?  I also set Response.Buffer = False, if

that would make a difference with a component...



Thanks for the advice, o gurus.



Regards,

Arbon Reimer