> >It is laudible that so many of my peers are applauding the decision of removing VFP from Visual Stiudio, however, I guess I stand alone in forseeing database customers of the future, living with the weaknesses of MS Access, or being royally shafted by the license costs of SQL Server, Sybase, or Oracle, because they do not know about middle tier tools (and trained developers) that are available to save them money and handle their data needs. >The lack of training and publications is clear evidence of this. Making VFP 7.0 a stand alone package with result in even less exposure to the product that it would were it still included in the VS pachage, even though it was never fully integrated, and now never will be. > >Microsoft has never effrectively marketed VFP as being an integral part of VS, and I have seen no indication that they will do so in the future. Microsoft is now cementing us VFP developers into a niche market, one who deals mainly with legacy applications, I guess the big attention will be on the re-training of the VB programmers, and pushing yet another programming subset, C-sharp. FoxPro use will attract less and less new customers because of less exposure. > >My lone vote is to keep it integrated, keep it in the VS package, and increase the marketing effort. It is a good product, better than many others, and should be strongly supported.
I guess you have not followed the messages from Robert Green. Read the interview that Evan Delay did with Robert and Ricardo. MSFT is strongly supporting VFP and will market it. How much is anyones guess right now.
The good news is that VFP will be out in May instead of August/September when VS.NET will be released.
