Posted by pbd22 on 04/12/07 21:22

On Apr 12, 1:38 pm, Hugo Kornelis
<h...@perFact.REMOVETHIS.info.INVALID> wrote:
> On 12 Apr 2007 11:46:57 -0700, pbd22 wrote:
>
> >I am following up my own message with more detailed info.
> >If some """kind""" soul could tell me how to isolate a range
> >of rows for each of the following conditions I would really
> >(**really**)
> >apprecaite it.
>
> Hi pbd22,
>
> Some kind sould has even written a whole web page full of methods to
> achieve this. The first part of the page focuses on ASP techniques, but
> the second part covers DB techniques for paging.
>
> http://databases.aspfaq.com/database/how-do-i-page-through-a-recordse...
>
> --
> Hugo Kornelis, SQL Server MVP
> My SQL Server blog:http://sqlblog.com/blogs/hugo_kornelis

Thanks Hugo (horay for kind souls).
I will go through this in detail after I get home. But, for now,
I am wondering if it is more cost-effective to do the paging logic
on the client or the server? I have already written all my paging
logic
in javascript (basically, what that link provides, but in javascript).
Do
I save on performance by moving the paging away from the server
or do you think it matters?

Thanks again.

[Back to original message]