The vast majority of the development world believes that local data munging is bad- because their tool can't do it very well. Why don't you go and provoke them?

For god sakes, you've got it backwards. Many believe stored procedures is the best approach, because it IS is the best approach...not because they had to resort to it. Assuming a good database server, stored procedures are generally the way to go.

While every developer community has its quirks, sacred cows, and what-not - this community has perpetuated a significant amount of myths and half-truths regarding .NET. If someone came onto the Foxforums and made similar comments about the capabilities of Fox, they'd be flamed to the nth degree. (Think back to the mid-1990's when Access pepole thought Access was just as strong as Fox). Don't dare say otherwise.

I'm not quite sure what you mean by "some of us have done a lot of work comparing and contrasting these matters". Can you describe this? (I'm not doubting you, I just don't understand what you mean).

I can certainly describe and even quantify the contributions I've made to the community (here, my articles, my presentations) on effectively moving from VFP to .NET. and building database apps in .NET/SQL.

I have a standard session I've done a half-dozen times on ADO.NET 2.0/SQL2005. Each time I've received feedback and follow-up emails from attendees (some of whom were VFP people) that agreed that stored procs are always the best way to go. So even VFP people believe heavy local data munging isn't the best practice. ;)

I'm done...last word belongs to you.


Kevin