Hi John,

>Really?
>
>A question was asked and I gave my opinion - which was entirely reasonable.

Did I question your right to voice an opinion? No.

>NOTE...I did not say I agree with with the assessment. Rather, I simply stated my opinion as to what I THOUGHT he said. FWIW, I don't think it is career suicide either.
>
>All that aside, what can you do in VFP that you cannot do in .NET today?

Oh, man, you know as well as I do ... why ask the question? Native data, inheritance advantages, macro substitution, et al.

>It is interesting that you, a MS employee, have no gone on record to say that VFP is a good training grown "for moving on someday"

Yup. Because computer languages don't last forever. Witness DIBOL, ADA, whatnot. What, you think they do? Or that by stating such I expose some startling revelation? Jeez, John, that's tabloid.

Allow me to be crystal clear. I work on the Fox Team. My customers are the VFP community. I was a significant member of that community before I joined MS and that's where my loyalties lie. I will always state things the way I think benefits the community and my employer be damned.

>
>>That was a bit abrupt, John.
>>
>>I would disagree, of course. Even if VFP died tomorrow, experts in the language gain core competencies that can be applied to a wide range of IT endeavors. We can do things in VFP that .Net won't see for years ... VFP is actually a great training ground for moving on at some point .. or not as the situation dictates. It's definitely not career suicide, man.
>>
>>
>>>>hi to all
>>>>since 2 years i m using Visual FoxPro for Development.
>>>>i had Interview in one Company.Interviewer Said to me You Are Killing Yourself.what does it mean.
>>>>
>>>>regards
>>>>Mazahir
>>>
>>>
>>>I think what they are saying is that by sticking with VFP - you are committing career suicide...