I love fox but MS does not love it the same as it love other products of their own. With that scenario, the two way street will not work for a relationship to grow and to last longer. Well, we must understand that MS is a business entity and they know very well why is that way?

It's a pain to see our FOX products is now in MAINTENANCE MODE but we must go on with life. Our .NET versions is underway and will be released sooner than we expected now that we learned its intricacies and how to do it in a different approach. Our goal now is to become equally productive the time when we do it in FOX. It's a painful process but that's life.

>Jess,
>
>When you have to start jumping through hoops to convince people that Fox is still supported and that the proof is hard to come by, that should speak volumes.
>
>Seroiusly, what does it really mean to support the product until 2010??? You certainly cannot say it is being innovated or that it is part of the strategic direction of MS.
>
>What I find astonishing is that most people that advance that as a reason to stick with Fox would not accept that one proposition if it applied to some other aspect of their lives. This is the trap people fall in when they only have 1 tool in their arsenal...
>
>And finally, if all you have to hang your hat on is "support until 2010". Just looking at that, isn't accurate to say that .NET, during that same time, will be supported more? On that basis alone, the "go with Fox because it is supported until 2010" argument must fail.
>
>John
>
>
>
>>You know that's the hard part of staying in VFP arena, a proof of support from MS is becoming a norm rather than exception. It seems that VFPers should always have Links, Whitepapers, etc. in hand just to close deals. The impression seems that VFP becoming a weapon that soldiers won't use if there is no certification that it really fires.
>>
>>>
>>>Regards,
>>>Gerard
>>>
>>>
>>>
>>>>Hi, Gerald,
>>>>
>>>>Out of curiosity, what specific reasons do you have for seeking this?
>>>>
>>>>Thanks,
>>>>Kevin