Re: Mysterious OLE DB DBID propids

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

  • Next message: Erland Sommarskog: "Re: Include Isolation Levels in ConnectionString" 
    Date: Sun, 6 Jun 2004 22:53:58 +0000 (UTC)

    Dave W (dave@w.com) writes:
    > Have been doing some more research on the problem by "redirecting" the
    > strange request to SQL Server to gauge its response (inside of the call
    > to my IColumnsRowset::GetColumnsRowset method). SQL Server doesn't
    > known about the optional columns either. It returned DB_E_BADCOLUMNID.
    >
    > When I returned that to ADO, it didn't go over too well.
    >
    > A little more background, this is a provider that often returns
    > hierarchical chaptered date. It works in most cases but the combination
    > of a hierarchical return rowsets combined with a client cursor causes
    > ADO to make the decision that the "provider does not support this
    > operation" upon executing the client side cursor command.
    >
    > If the return value is not hierarchical in nature, client cursors work
    > just fine. Thus me implementing IColumnsRowset to see if that would fix
    > the situation.
    >
    > I'm really hoping the answer is not "only the MS shape provider is capable
    > of this behaviour".

    Thanks for the supplementary information. I have yet to hear something
    from Microsoft on the issue, but it usually takes some time to get answers
    to such questions. I'll post back when I know anything more. If you prefer
    to be alerted by mail, just drop me a line. 

    -- 
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: Erland Sommarskog: "Re: Include Isolation Levels in ConnectionString"

    Relevant Pages
    Loading