>>Ok. Should I continue to invest my time in VFP well into the future. Your opinion/suggestion?
>
>Sure. VFP 7.0 is a great version, and Microsoft is working on a new version (VFP 8.0) with many new features and functionality. But really, this is a question for you to answer. But remember that I am bias towards VFP. Asking me if you should use VFP is like asking a used car salesman if you should buy the used car you are looking at. You should know the answer already. :)

Really Ken, I don't know the answer, thats one of the purposes of creating this thread - to get a sense of direction. I am a relatively new developer and have chosen VFP. When you see threads like "Decline of VFP" there are negative connotations associated with the product itself. I may be wrong - but thats why I started this thread.

Further, you suggest that VFP developers get MSDN subscriptions. If so, why can't VFP be part of the Visual Studio package? Separating VFP from the Studio package by itself may have contributed to differrenmt interpretations of the life of VFP.