>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,
Couple of ideas...First, you could list all the records on the same page, 10 to each view, and anchor each 10 record set so it drops down and up on the same page for each anchor. Second, you could key the record set for each 10 records, so refreshing the page would send a parameter that the existing RS would use to display those records keyed to the variable. Use a frame where the top holds the record set, and displays each 10 record set to the lower frame. You would only have one pass to the server, and you would have control over which 10 were being displayed below.