>Perhaps, but I question the relevancy. When I go about solving a problem, I don't think in terms of whether what I am doing conforms with a world wide standard that has little or nothing to do with the issue. You are going to have to back this up with some concrete advantages.

First of all, lets take your argument to why VFP is materially disadvantaged to VB.NET. If I understand correctly, it stems from the fact that VFP is not on the list of "approved languages", no?

In that case, I can use the same argument against VB.NET. I've already heard of developers saying that C# could be used for projects where VB.NET could not due to govnermental mandates (I don't know what country this developer was in, thouhg). I see this as the trend for two reasons, one, its very similar to Java and C++, and two, it truly is a standard, noproprietary language.

While, I admit, its stupid of decision makers to let C# in but not VB.NET, thats the reality. VB.NET can do just about everything (but not all) that C# can do... but then... so can VFP.