Perplexity on relation over a select count

I need to get the child of parent/child relation and I've some perplexity
about the best method to use.
The classic (select count(*) id from table where id = a.parentid) nested
into a select generate a lot of
roundrip if used for a large set of results, but for small search is quite
good.
But what about the new ado.net relation table? Is more efficient? What does
it do internally?
Take on mind that I'm working over a 2003 access database, so the choice
cannot use SP as well as complex results set that return table object that
SQL server can return.
Thank you
Andreaperhaps you should post your question to one of the 'ms access' forums. You
may have better luck.
-- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"andrea" <googlegroups@.freemail.it> wrote in message
news:9fa0d7351833f8c812a7cff697bc@.news.microsoft.com...
>I need to get the child of parent/child relation and I've some perplexity
>about the best method to use.
> The classic (select count(*) id from table where id = a.parentid) nested
> into a select generate a lot of
> roundrip if used for a large set of results, but for small search is quite
> good.
> But what about the new ado.net relation table? Is more efficient? What
> does it do internally?
> Take on mind that I'm working over a 2003 access database, so the choice
> cannot use SP as well as complex results set that return table object that
> SQL server can return.
> Thank you
> Andrea
>
>