IF that is true, then I applaud MSFT's goals. I do most of my programming in VFP and about 35% of it Delphi. The entire parent corporation is the same way. If it is client/server or small business (especially small business) we use VFP. If it is in anyway web-enabled or relies on the windows api, we use Delphi. Having used a 'fox' product since 1985, VFP is my preferred tool. However, I cannot justify using VFP in lieu of Delphi for those other two requirements. While, I would ABSOLUTELY LOVE to see VFP compete in those two areas, to do that, the same capabilities in Delphi need to be in VFP. Also, due to Delphi's low overhead, the powers-that-be are pushing Delphi over VFP more and more.
Tracy
>>FYI, the presentation in Brazil had 98 people, who loved what they saw... at the end of the presentation, when I asked who'll upgrade to VFP 8 once it gets released, almost everybody raised their hands (maybe everybody... there was too many people in order to let me count everybody). :)
>
>Awesome community efforts Claudio, thanks! Beyond VFP developers, we want FoxPro 2.x, Clipper, and Delphi developers to move to VFP 8.0. I know Latin America is a prime target for these groups of developers to target.
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"