>>>>>My boss is very concern about the future of Visual Fox Pro. Is Microsoft planning to keep Visual Fox Pro or are they planning to do away with it? Can you point out any articles that would help me answer this question. Thanks.
>>>>
>>>>
>>>>"The Visual FoxPro Strategy Backgrounder" -- released by MS sometime in November reaffirms MS commitment (just lack of savvy marketing) to Visual FoxPro. You can obtain this paper at the Microsoft website Visual FoxPro page and -- I think -- somewhere here in the UT. Also, version 6 (Tahoe) is now in beta test and version 7 is on the drawing books. These are facts.
>>>
>>>The questions about the "uncertainties" about the future of VFP seems to be creeping up more and more here in the UT (almost daily)! As a user since verison 1.02, I too love using VFP. My feeling is that even if M$ decided to kill VFP in the near future (however unlikely), there will be a lot of people like me who will still use the tool for years to come. I bet there's still a lot of companies depending on an old and reliable 2.6 DOS apps build years ago that have been modified since.
>>>The point is, no matter which way the wind blows, for most developers there will be ample time to learn another quality tool when that time comes, if you haven't done already.
>>>Who knows, maybe M$ will create a great VFP 7.0 and decide to call it VB 10.0. Then I will use VB 10.0. It doesn't matter what M$ call it, we'll all know it to be VFP 7.0, a "Wolf in Sheep's clothing".
>>>
>>>Just a though.
>>>John.
>>
>>
>>Stop the VB/VFP will merge stuff. They will share common tools in the future (screen builder, etc), but the two will not merge.
>
>Relax Craig. If you somehow got the impression that I was in anyway implying that VB and VFP will merge into one product, I wasn't. I was simply trying to express my opinion that maybe we shouldn't waste so much effort trying to guess what M$ is going to do or not going to do with VFP (or any other product for that matter). Any future decisions M$ makes regarding VFP or any other M$ product is their decision and I, as a developer, don't have much to do with it but accept it and adopt to it.
>
>In addition, I've read somewhere that new version of VB's OOPs features are "borrowed" directly from VFP so EVEN IF in the far distant future M$ decides to stop marketing VFP (again I say unlikely), what we learned from using VFP now will not be lost but can be directly used to learn some new tool (VB or whatever tool it might be).
>
>Please don't focus on just one part of the message (the part I was trying to be sarcastic and bit humorous w/o being successful, I guess) and read the whole message as it was meant to be read.


A couple of things:

- Someone reading a thread about VB & VFP merging may think that is what will happen..therefore, I avoid joking about it

- I think you need to check what you read about VB 6.0's OOP capabilities. I read the same thing. The article was dated April 1. VB is not getting anymore OOP than it is right now.