>I need to display data from an ADO recordset within a web page, via ASP. This I can do, no problem.
>
>What I'm trying to do is reduce the hits to the server.
>
>For instance, I have one ADOR that returns 150 records. The client wants to see 10 records per page with buttons to go to the next/previous pages. Since the recordset is disconnected how do I basically save the recordset to the client and have the next/previous buttons get the data from that source rather than hitting the server over and over again?
>
>Any ideas what I might get this done?
>
>Thanks,
>Michael

Michael,

take a look at http://www.learnasp.com/learn/dbtablepaged.asp It has an example using paged recordsets. This might be a solution to your problem. It's how MS does it on the support site (more or less). They instead us hidden form values, but this gives you a good push in the right direction.

Hugo