>Exactly - you need to break away from the RV to serve data to the UI. This is yet another reason why RV's IMO, don't "cut it.."

Unless you're only serving up ADO to the front-end you need to do the same thing with ADO calling stored procs.

> My point is that if you are engaging in "real" n-tier development, RV's provide an extra layer that does not provide requisite utility. i.e., if you are going to have serve data to the UI via XML, ADO, etc, why not use that in the first place?

For true, distributed n-tier development, this makes a lot of sense, but I still wouldn't view it as the only way to accomplish this. For typical 2 tier client server apps or n-tier apps that expose the data as properties of the business objects, I think RVs can still work well.

Also, what if I can't assume the client has ADO or is even running a machine that is capable or using ADO?