>Hi Peter,
>
>>1) Is the VFP community strong enough to develop VFP further if we had access to the source code?
>
>Nope. We make money by developing VFP applications, not by developing VFP.
>
>>2) What are the chances of selling Microsoft on turning VFP into an open-source test case?
>
>more than bad. VFP is too much integrated into other Microsoft technologies and Microsoft won't sell them.
>
>>3) Anybody interested in this?
>
>Probably not. First, I don't think it's necessary since Microsoft is pushing VFP in the last couple of months. Second, when microsoft would decide to stop VFP, most of us would probably either continue with the last version and then start looking for new tools, like VB, VC++, VJ++ or Delphi.
>
>Christof


Thanks to all for offering their answers. I think the most telling point is that the VFP code overlaps a great deal with all of Visual Studio. Even if MS were ready to give up some control over VFP, I can see that they would not want to do that with the rest of the components.

Peter