>No, it's not "pretty much agreed upon" by those that "actually do the work". I used to support this technology, speaking with those outside the ivory tower every single day. I'm well aware of what's being done in the real world.
>>
>
>It is pretty much agreed upon by those who write in VBPJ and SQL Server Magazine..
>

JVP,

Thpis is not directed solely at you, but at all the people in this thread who know a whole lot more about ADO than I do, and are caught up in a heated environment. Please don't take it as a chastisement of your behavior as opposed to anyone else who's been involved in this fiasco.

No one (well, at least speaking for myself) is failing to recognize your mastery of the subject matter. However, the presentation on both sides of the argument has fallen to levels that my 8 year old niece would not be proud of.

I don't know all the history, and wasn't at the Wednesday presentation. In order to make this more palatable, and to give us a chance at building a collaborative summation, where people can go back and reword or edit their own comments when the heat of the moment has fallen away, why not build a wiki document as a collaborative effort, so we all get the benefit of multiple valid points of view without the immediate negative knee-jerk response we all have when we feel challenged being locked in for etermity.

As someone who doesn't have a great deal of mastery of ADO and its application, I for one would get a lot of benefit from the ultimate product of such a collaboration.

It's possible that there's simply too much emotion to do this effectively. If that's the case, spinning wheels and driving up mesage counts here on UT isn't helping things, either.

I'd take it as a personal favor if you'd consider this, or some other, similar mechanism, to build a really solid, collaborative summary of the place that shaped recordsets take in the scheme of ADO implementations. I'll read it, promise.

Thanks,

Ed