>In the August issue of FoxPro Advisor, Kevin McNeish spells out in his article "Visual FoxPro and .NET" all the reasons he thinks .NET is better than FoxPro.

Yeah, I just read it yesterday, very good article. But I would not say Kevin is saying .NET is "better," I think you're putting your own "spin" on the article when you say that. (though I'm not inside his mind, of course) He emphasizes the qood qualities and strengths of .NET (and a few of the same about vfp), but that's what the article is about, learning more about .NET.

He's not dwelling much at all on vfp because most of us already know what it can do, but many of us do *not* know much about what .NET can do. He is trying to educate us better on .NET, and many of us (myself included) need more .NET education such as Kevin's article provides (sort of like ".NET 101," were this a college freshman course)

At least that's my take. (Like when you read the section "What's so great about vfp?", it seems to me quite fair-minded, gives vfp proper credit for what it's best at, and is not saying .NET is a superior product - in fact, he lists .NET short-comings). My take is more that he is just advocating learning more about .NET, which is a very logical thing to do these days.

I think he did a good job of balancing some of the ups and downs of each tool, and I came away with the attitude something like: "these are both good tools. Each one may be more suited to specific situations, but they're both good tools. Because .NET is fairly new, you should maybe focus on learning more about it." And perhaps I would add, "these tools can work together in a very productive way, once you learn them both."

So *my* take is that he is just saying we should broaden our horizons by learning more about .NET., what it can do, and he is not implying to uninstall and throw out your vfp copies. In this regard, I think Kevin is right on target.

>Perhaps every item on his list, or almost every item, could be an enhancement and incorporated into the next FoxPro version.

Maybe some, yes, but we have discussed ad nauseum the fact that we'd have to sacrifice many of vfp's best features to do this, so that if all .NET ideas were incorpoarted, vfp would no longer be needed at all.

But I certainly agree that they should be looked at, so that we can add any .NET-style enhancements that do not sacrifice major features of vfp.

I once joked we should have 2 versions of vfp, one staying purely data-centric as it is now, the other incorporating most .NET features, losing some features as needd, and added into VS.NET.

Not so much of a joke as I thought at first. Now that seems like the one thing that would make everyone happy, if the 2 versions could work together reasonably well...

BTW, don't worry, I'm pretty sure Ken's read Kevin's article by now, and if you really wish to contact him, he can be found right here at the UT fairly often.