>
>>Like you, I can't stand "percolating ADO recordset up the chain" (great phrase, btw). As a result, I make pretty extensive use of the ado recordset's GetString method, which generates the data as a delimited string. This makes it easier to pass the data around (including by value), and will work for multi-record sets. (Unfortunately, you also need to tag on field names and types, which GetString doesn't do -- I throw 'em onto the end as a "last row.")
>
>This is a useful tip that I'll stash away in my favorites. *g* Thanks.
>

Sure. What I didn't mention, but should have, is that in many cases, just passing XML will be simpler. But I frequently end up working with legacy objects that expect ADO recordsets or legacy code that already include a lot of ADO maneuverings, so this approach is a goodie in those cases.