>Some open-ended questions...
>
>1) Is the VFP community strong enough to develop VFP further if we had access to the source code?
>

I seriously doubt it - even if we had the necessary talent, I doubt that the people with the needed skill and background could afford to quit their day jobs to work on an open-source product. And of equal importance, we need fixes and enhancements on a regular and timely basis in step with changes to other MS products. if you think you've seen delays in delivery now, just wait until getting a release together becomes a back-burner issue for everyone involved in the project...

>2) What are the chances of selling Microsoft on turning VFP into an open-source test case?
>

Virtually nil - there are too many things in VFP where MS would want to be able to vigorously defend their intellectual property rights, and too much of VFP is shared with other pieces of Visual Studio to be able to release it without releasing the code for shared components of Visual Studio, too.

>3) Anybody interested in this?
>

No thanks.