>>>>>>>>>>>>>>>>>>>>>
Let's not forget, despite MS's every attempt to kill it passively, VFP won't die. VFP is, whether some companies realize it or not, a vital component of the Visual Studio.
>>>>>>>>>>>>>>>>>>>>>

You might be right (I differ a bit on you choice of the word "vital" but that's mainly semantics). But, I need to be honest here -- as someone who works on a consulting basis for several companies, in work that includes interviewing potential programmers -- I would not hire someone who only knows VFP. Sorry, but it is true. In two companies I work with, other languages (mainly VB) is increasingly integrated with VB. In another, I suspect that VFP will not be the primary language in the future....

Sorry, I just need to be honest for anyone out there, especially a somewhat lower-level coder, who is wondering what prospective employers are looking for (even a VFP guy like myself): Visual FoxPro by itself is not enough. I certainly am not the only interviewer in the world, so don't take what I am saying as gospel truth.... but I have recently decided *not* to hire several VFP folks because of lack of breadth. I don't think I am the exception on this point. If you are a VFP person with a few years of work under your belt, wondering what's next, not committed to your current company.... I don't think that FoxPro will figure as the exclusive language in your arsenal, practically speaking.