>If those companies can expect their applications to run and be supported for another 8 to 10 years I don't see why they should have a problem. All systems have a life cycle of redevelopment and moving to a new set of tools shouldn't be a huge hurdle over such a long timeframe.

Suppose a company has to decide THIS YEAR to either modernize its in-house-built VFP7 application that handles complex rules, or to choose for replacement with a standard application that only claims it can handle those complex rules...

What do you think will be the influence of the announcement made this week?

And how do you think developers and decision makers will currently feel if they had that decision to make LAST YEAR and chose to continue using VFP?


>VFP was nothing like earlier versions of foxpro so required as much change as going for VFP to whatever else.
>
>My main sadness is that th VFP community that I see here always seems very helpful and supportive and I don't know if that will carry on in the long run. I think that change is really been happening for some time, there is still excellent help here but I don't think there is as much as there used to be .
>
>Nick
>
>>There are quite many companies that market complex, in-house built with vfp, off-the-shelf products. E.g., two of the leading Dutch bookkeeping packages are entirely written in vfp.
>>
>>These companies now have a really serious problem. The MS decision to stop with further develpment of vfp forces them to invest heavilly in completely rewriting each of their complex packages. Has this problem already got the focussed attention of us all here?
>>
>>For example, does law permit MS to stop further development? Isn't there a case when such a company goes to court, because it feels misled by MS? Afterall, MS has claimed many times in the past that vfp would not gonna die. Those promisses have led decision makers in those companies to decide that it was okay to use vfp as the primary programming language for the development of their complex packages. And now they feel forced to switch to another language, not in 8 years, but starting this year already.
>>
>>And how about those of us who have successfully tried to convince customers that they can extend or modernize an existing vfp application, making it unnecessary for that customer to seek for a complete replacement. Those customers will gonna feel misled, by US, rather than by MS. And why did we make those promisses? Because there were no clear signs in the past that MS would gonna drop further development.