I thought they said (after the initial announcement) that they would release service packs to fix major incompatibilities with future versions of Windows. Am I misremembering?


>Nick is right, there's absolutely no consideration by MS whether or not a new OS version is compatible with VFP. None.
>
>OTOH, VFP is fairly generic in terms of the way it interops with the OS so if MS plans for general backwards compatibility VFP will be dragged along for the ride.
>
>The real future compatibility issues are probably not with the core of VFP, but with the external components it relies on, such as GDI+ and SOAP. Keep an eye on how well they are supported and it'll tell you a lot about how well VFP will be.
>
>
>>>>(My apologies if this has been discussed already). Can somebody shed some light on just what it means that VFP will no longer be supported after 2015? In particular, when the product is no longer "supported", does it mean that Microsoft gives itself license for incompatibility? Is MS saying that beyond 2015, it might produce versions of Windows no longer compatible with existing VFP apps, so that apps created today with VFP8 or VFP9 would essentially no longer be usable?
>>>
>>>My interpretation is that they wouldn't deal with bug reports after then. Support for foxbase and foxpro2x have already been stopped but there are foxbase, foxpro2x applications still running successfully all over the world. Same goes with the VFP versions whose support have been dropped.
>>>Producing incompatible versions would mean those windows versions wouldn't support any win32 application, not just VFP.
>>>Cetin
>>
>>I hope you are right!!! But I'm wondering, just because foxbase and foxpro2x apps still work in WinXP, has MSFT made a commitment to keep the OS compatible with them, or have users just been lucky so far? Imagine how we all might feel in 2013 if suddenly MSFT announced:
>>
>>"Oh, by the way, it looks like the new architecture we'll use in Win2015 will break all VFP apps. Sorry. But nothing we can do about it. Has to do with some unusual API implementations, deep under the hood, that only our VFP development team did. We suggest you start migrating to .NET and SQL Server."
>>
>>I would like to know that MSFT is absoultely committed to keeping future versions of Windows compatible with today's VFP apps for the next 25 years or more.