This is why we *need* to be able to hold conversations without saboteurs bursting in. One reason why autospanning datasets is "obvious" to me is because I need it all the time. Whereas all the cool work you do with components and UIs is as nothing to me. Perhaps the converse applies as well. But we'll never know, because every time we try to discuss it "somebody" bursts in calling people paranoid, uneducated, and all the rest of it.

I understand. I think we're just going to have to "agree to disagree" on this. I do much more work in stored procedures now than I did even 3 years ago. Perhaps I'm fortunate because the companies I've worked for have some pretty impressive server environments. I'm doing some work for a bank right now where we're able to do the vast amount of processing and grouping in stored procs.


Yes, in the very beginning, I turned to SPs because you can't do full-blown SQL in ADO.NET. But along the way, I came to realize the value of doing so (SPs), to the point where I'm more efficient doing it that way and wish I had turned to SPs earlier.

For many data processes I can set up my own development/test environments, and can often implement changes...often without touching the application. This has certainly pleased clients.

Would this be less desirable in lesser server configurations? Maybe. I used to often say (and maybe I haven't said it enough recently) that a .NET solution may not be practical in an environment with large data but "limited" hardware resources, especially on the server.

Kevin