>>
>>Not if the data object constructs the properties on demand, and the interface provide a set/get. Then you get an object-object independent of any data standard.
>
>Yes, I agree. However, if you're returning large amounts of data, it could get messy.

Well, not really. How the data object maintains data sets is up to it. So, it might well keep an ado recordset. I just find percolating ADO recordsets up the chain to be awkward. That's purely personal preference, though, and as I think I mentioned elsewhere, one needs to know just what sort of ship one is building.

I'm not a fan of building every app for every scalability. The overhead exceeds practical project limits for enough apps that I think one can go overboard.