>
You said it was "one of many reasons". What are the other reasons, besides the declining usage?
<

I don't need to cite other reasons Mike. The point has been made. Just because you ask, it does not follow that I will provide. For a long time, I have already favored other tools for some tasks over VFP. For example, anytime I need events or I need to interact with WinAPI, I will rely on VB. Will I still use VFP for other things? Yes. I could cite many reasons, as could others. Buy why when the point has been made?

<<
You keep saying VB.NET can do evrything C# can do. What can't VFP do that those two can?
<<

You need to slow down Mike. I said in all material respects, VB .NET can do whatever C# can do. Obviously, if you need access to some pointers, run unsafe code, you will need C# for those pieces. When I say material, I am talking about those things one normally does in db app development.

As far as what VFP can't do, start with VB 6. VFP does not support custom events. The support for accessing the winapi is sub par. As far as .NET is concerned, I can use the .NET classes natively in .NET. I need COM/Interop wrappers to make use of them in VFP. I don't know what you are looking for Mike...

>
I advocate all .NET developers to make sure they're famailar with C#. Why? Because it will be much more beneficial to companies to standardize on a language, and if the choice is between C#, VB.NET, and VFP, C# is easier to standardize on because its a standard and very similar to other industry standards.
>

Your analysis is too complicated Mike. All .NET developers should learn C# because of the relationship it has to .NET itself. The reasoning is more of common sense than anything else. xBase was never standardized and I continue to use it.

I think the benefits you perceive are more theorhetical than practical. You say that companies should standardized on C# because it is based on a standard? Why? How about issues of productivity? Do they play a role? I think they do...

Name some tangible benefits a company gets that would not be otherwise realized though this standardization argument you are making. Kevin and others have tried this argument. And perhaps at a certain level, it may have merit. But this is not the forum for that. I contend that for the independent consultant, it does not amount to much...

When I see folks saying that they choose C# because it is not VB, I make the inference that those folks are not all that informed. In jest or not, I do get the feeling that many have based their decisions on this type of flawed thinking.