>>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.
<

That is not my argument. VFP is disadvantaged...period.

<
If I understand correctly, it stems from the fact that VFP is not on the list of "approved languages", no?
>

Choosing a langauge that is more likely than not to be on an approved list is not a wise move IMO. This is but one of many reasons.

>
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).
<

It is not the same argument because you have taken VFP out of the mix. It does go to the point that developers should learn both langauges. Choosing between VB and C# does not change the state of affairs for VFP, and that is central to my point. I would also say that while you can point to specific cases, one cannot and should not create a per se rule against VB.

<
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.
>

Using that logic, folks should have never chosen langauges like VFP or VB. If I had to right now, I could not code in C++, but I could code in C#. The key is having the framework. Again, I think you place too much on how much a like langauges appear. The argument works well for VFP to VB, because there is a track record for that. The likeness you see I believe is semantic at best. Your case study should be one that finds somebody who knows C#, knows nothing about Java, and can get productive in Java right away...


>
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.
<

Again, VFP has to be able to get through the front door first.. And, if the requirement is to base apps on the CLR, VFP cannot do that either.