You have to be flexible, learn multiple tools. Techniques and concepts usually transcend the tools you use. IMO, with respect to using the best tool for whatever you need to do, then the future of that tool is irrelevant. As for MS Support of VFP, start by clicking the links in my signature line below.

>My personal goals are to get my programming/software knowledge up-to-date, and as a former FPWer, I decided to pursue VFP. Compared with other languages I’ve learned over the years, I get very excited about VFP. Rarely a day goes by that I don't remark to myself "Hey, that's pretty cool!" So I come to the UT boards with that background and interest, and run into this VFP - .Net debate.
>
>In a previous post, John Petersen said to George Tasker: "On a pure technical basis, many arguments can be constructed that validate the feeling that VFP is in an enviable position. These arguments are mostly klinged to by people from the inside. For the most part – the business - and quite frankly the technical world as well - are not ruled by "technical" concerns..."
>
>This hit home to me. I don't care how great VFP is technically. If
>businesses and students (like me) PERCEIVE that VFP isn't the future, businesses won't support it and students won't learn it.
>
>So, I've been rethinking my pursuit of VFP. Can I better spend my time learning something else? What will be best for my future?
>
>Microsoft's confusing marketing/support of VFP casts doubts, whatever their intentions may be. Even the VFP community of experts, are obviously confused/concerned/doubtful. Microsoft appears to have some kind of plans for VFP – they are planning v.8. They are clearly marketing .Net. But I haven’t heard from them a clear statement as to what application, role, or niche VFP will have in future.
>
>So that’s one student’s opinion. I would love to hear from all of you what advice you would give folks like me.