RE: "cannot fetch chapter column" (for MSFT)
dave_at_w.com
Date: 07/07/04
- Next message: SqlJunkies User: "Re: Outlook 2003 breaks OLEDB for Internet Publishing?"
- Previous message: Erland Sommarskog: "Re: OleDB Parameter Error with C#"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 6 Jul 2004 17:49:02 -0700
Anyone?
"Dave W" wrote:
> Hi all,
>
> I'm hoping someone from Microsoft (or others in the know) can tell me why
> ADO is returning "cannot fetch chapter column" (0x80004005) when requesting
> hierarchical disconnected data from the OLE DB provider we have written.
>
> First of all our driver works fine when returning hiererarchical data to ADO
> as long as you don't set the connection's CursorLocation property to
> adUseClinet prior to issue the command that returns hierchical data (we have
> implemented chapter column, child rowsets etc.)
>
> We were initially getting an error which stated that the provider was not
> capable of the requested operation (or something along those lines).
>
> After some research, it seemed that ADO might stand a better chance of
> dealing with disconnected hierarchical data if our provider implemented the
> optional rowset interface IColumnsRowset.
>
> I went ahead and enhanced the provider to support that interface and ADO
> does in fact use it (if and only if the connection cursor location is set to
> client cursor).
>
> The message that we're getting now is "cannot fetch chapter column"
> (0x80004005) during execution of the query.
>
> What else does ADO need for it to be able to consume disconnected
> hierarchical data????
>
> TIA,
>
> Dave
>
>
>
>
- Next message: SqlJunkies User: "Re: Outlook 2003 breaks OLEDB for Internet Publishing?"
- Previous message: Erland Sommarskog: "Re: OleDB Parameter Error with C#"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
