need smarter paging

I have a query that returns many thousands of records, a broad search
result. The web interface is fine with it because I use a paged grid view -
however this control cannot tell the app server to just return the records
that it's going to dispaly, it returns the whole result set, which large
enough to cause a communication performance problem between the app server
and the web server.

SO...

I really want to be sure that there isn't some existing, built-in design
structure I can use before I go re-invent the wheel, put paging into the web
method, or the query itself. What's the most commonly accepted practice?

Paul


.

Relevant Pages

  • Re: getting support
    ... this is the misleading msg thrown up by the MS web interface ... when you click to post a new query or to reply: ...
    (microsoft.public.excel.newusers)
  • Re: communicate with Prolog engine in Prolog
    ... something like a metainterpreter. ... Suppose users may query a Prolog program through a web interface. ...
    (comp.lang.prolog)
  • Slow performance with web query
    ... Whenever I open the "Query the Catalog" ... Now, if I try to use the web interface I created, if I try the same ... How can I get it to do the same thing the MMC Query Catalog Form is ...
    (microsoft.public.inetserver.indexserver)