Having worked through an example (I'm novice status), it seems that this is
less efficient than using hierarchical recordsets in normal ADO.

Can one still use hierarchical recordsets (using the SHAPE command) in
ADO.NET?

RE: Multiple Active Result Sets - general question by NoSpamMgbworld

NoSpamMgbworld
Fri Feb 03 09:36:43 CST 2006

"Griff" wrote:

> Having worked through an example (I'm novice status), it seems that this is
> less efficient than using hierarchical recordsets in normal ADO.

MARS serves a different function than hierarchical recordsets.

> Can one still use hierarchical recordsets (using the SHAPE command) in
> ADO.NET?

Yes and no. You cannot use it in ADO.NET, but you can still use the ADO
library in .NET. The downside is you end up with the Interop overhead, so it
is not an ideal solution if you can solve your problem in .NET alone.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

Re: Multiple Active Result Sets - general question by Sahil

Sahil
Sat Feb 04 12:00:39 CST 2006

First of all, MARS is a different concept than what you mention (just so
there is no confusion) :)

Secondly - ditto on whatever Gregory said.

- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.malik/archive/2005/05/13/63199.aspx
__________________________________________________________


"Griff" <howling@the.moon> wrote in message
news:uwIFYyKKGHA.2712@TK2MSFTNGP10.phx.gbl...
> Having worked through an example (I'm novice status), it seems that this
> is less efficient than using hierarchical recordsets in normal ADO.
>
> Can one still use hierarchical recordsets (using the SHAPE command) in
> ADO.NET?
>



Re: Multiple Active Result Sets - general question by Griff

Griff
Mon Feb 06 03:38:05 CST 2006

> Yes and no. You cannot use it in ADO.NET, but you can still use the ADO
> library in .NET. The downside is you end up with the Interop overhead, so
> it
> is not an ideal solution if you can solve your problem in .NET alone.

Hmmm

I've found hierarchical recordsets in Classic ADO to be such a powerful tool
that I'm really surprised that it's now possible to do this using ADO.NET.

Was I the only person using hierarchical recordsets?