I don't know how many of you have the same situation with the politics in your company regarding VFP. I do know that because VFP is not part of Visual Studio, our company has dropped VFP as a viable developement platform. On the other hand, they do support Access (yuck... double yuck) which is part of Microsoft Office.

I suppose they look at things as if they have a good backbone, like Visual Basic has Visual Studio and Access has Microsoft Office. The joint effort of the products makes them sell and be accepted by large companies. With VFP being added and then again dropped from Visual Studio, makes companies beleive that VFP is not going to be supported by Microsoft. Companies could look at it as, Microsoft has given VFP a good kick in the teeth by adding and then removing VFP from Visual Studio. A Death Toll. I personlly don't beleive this, but VFP without something else makes it a pretty weak sale. What if Microsoft took out Visual Basic from Visual Studio, what would you think - dead product? Mostly because VB has been part of Visual Studio for so long. Hence the bigger question, if VFP can not be part of Visual Studio, then can VFP be part of Microsoft Office or flavour of?

Given the choice, would an educated consumer choose Access or VFP flavour of Microsoft Office? It's obvious that Microsoft wants to support VFP in it's future, so let's see them support it by putting VFP (Basic version) against Access. In my opinion, it would be fair marketing. Let the best database application survive!