First of all, this is what I am doing. I wrote a COM component that

basically does searches against a database (via ADO) and returns the results

in XML format. My ASP search results page has an <XML> element mapped to an

ASP page that uses this COM component (a dynamic data-island essentially)

and it works great. I was just wondering if there is a way I can browse the

XML data-island 25 records at a time, per page (like GetRows in ADO), via

DHTML or something so I don't have to make another round trip to the

database. I don't want to make any more trips to the database than I have to

because there are, potentially, several hundred people doing searches at one

time and each search can return several hundred (if not thousands) records

at a time. In which case, any more trips to the database could be quite

costly. Thanks for any help or guidance!!!



Jason Olson

Internet Application Developer

jolson88@y...

xxx.xxx.xxxx

Nevermind, I found out how. For anyone who is curious, you set the

DataPageSize of the table equal to the number of records that should display

and then use the TABLE's following methods: firstPage(), lastPage(),

nextPage(), and previousPage().



Jason Olson

Internet Application Developer

jolson88@y...

xxx.xxx.xxxx



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

From: Jason Olson [mailto:jolson88@y...]

Sent: Wednesday, August 29, 2001 2:10 PM

To: ASP Web HowTo

Subject: [asp_web_howto] Browsing a disconnected data-island





First of all, this is what I am doing. I wrote a COM component that

basically does searches against a database (via ADO) and returns the results

in XML format. My ASP search results page has an <XML> element mapped to an

ASP page that uses this COM component (a dynamic data-island essentially)

and it works great. I was just wondering if there is a way I can browse the

XML data-island 25 records at a time, per page (like GetRows in ADO), via

DHTML or something so I don't have to make another round trip to the

database. I don't want to make any more trips to the database than I have to

because there are, potentially, several hundred people doing searches at one

time and each search can return several hundred (if not thousands) records

at a time. In which case, any more trips to the database could be quite

costly. Thanks for any help or guidance!!!



Jason Olson

Internet Application Developer

jolson88@y...

xxx.xxx.xxxx