I see the pros/cons of making VFP open source Claude. For us, I hope that VFP NEVER becomes open source (or at least not while I am working for a financial institution). We are not allowed to use any open source product. PERIOD. No one in the entire corporate structure is (all the way to our parent company - the bank). That was also the case when I worked for the government.


>Why not just make VFP an Open Source product and let it continue to evolve on its own? There still plenty of developers using it and making it better. MS would even get more points for doing something cool and being more in the spirit of current technology trends. I really believe the current half-hearted marketing/development of the product is dragging it down more than anything...
>>We have a wide variety of options to consider based on demand and what will be in demand in two years. We are working on this now, and once we have it worked out pretty solid we will make annoucements, probably 2Q of this year (between April and June sometime).
>
>>>Right - and this doesn't mean there is a new VERSION coming out, it just means there will be UPDATES coming out. VFP 9.0 SP1 for example. (maybe fix the data-session window refresh problem, etc). Usually I hear about the NEXT version of VFP, not just about 'updates'....
>>>Pure speculation on my part of course as I have no knowledge of what MS plans to do....I simply notice a pattern change as has Mike Beane and probably every other VFP developer.
>>