Re: ADO CursorType Problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Erland Sommarskog (esquel_at_sommarskog.se)
Date: 09/10/04

  • Next message: John Smith: "Frontpage edit button from IE broken" 
    Date: Fri, 10 Sep 2004 22:38:38 +0000 (UTC)

    William (wwells@gmri.net) writes:
    > What I want to do is fairly simple. I have a fairly large (2000+ row)
    > recordset that I need to page through 25 records at a time. each new
    > page will only get the next 25 records from the recordset. I would
    > like to do this server side using the .AbsolutePage property. My
    > thinking is that this minimizes the total number of records going
    > across to the web server.

    Which means that everytime the user presses Next, you need to make a
    roundtrip to the server, and in the meanwhile the user can go for
    another cup of coffee. Get 2000 rows the web server, and then page
    locally. It is not likely that user want to see more than 2000 rows
    anyway.

    By the way, I hate web sites that gives me only 25 rows at a time.

    > I don't really need a keyset, I could do this with a static as well,
    > unfortunately neither of these will work for me server side currently.
    > The only cursor type I seem to be able to get server side is the
    > default forwardonly/readonly cursor. My understanding is that this is
    > usually due to some issue with the provider. My database is SQL Server
    > 2000, so I know that the database supports this. My only other
    > thinking is that something must be wrong with the SQLOLDB layer that I
    > am using to access it.
     
    Did we actually see the query? For a cursor to be a keyset cursor, the
    query has to have an identifiable key, or else SQL Server will convert
    it to something it can handle. You can forget about the problem being in
    SQLOLEDB. 

    -- 
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
  • Next message: John Smith: "Frontpage edit button from IE broken"
    • Quantcast