David:
Thanks for the game plan clarification. Although I pretty much assumed that to be the case, it is good to see it stated, even informally.
The real "rub" comes after 2015 when the fuse has finally burned out -- that's when the DNR (Do Not Resuscitate) order will be in full effect. i.e., if the poor old Fox's EKG goes flat for any reason, I don't expect MS to take any "heroic measures" to keep the beast alive, much less resuscitate it... Hmm, maybe I'll put a call in to PETA for Microsoft's animal cruelty :-) :-) :-)
Pertti
>Pertti,
>
>>...If all MS would do is set up a "VFP runtime maintenance" group which would only need to spring into action if a new Windows version breaks something in the runtime modules...
>
>We actually have that in an informal kind of way. If Product Support Services identifies a major app-breaking fatal flow in the future that does not have sufficient workarounds, it will be escalated inside Microsoft to the VFP email alias.
>
>Anyone at Microsoft who watches that alias and has the expertise to handle it will then be prioritized into action to investigate and try to find a solution. This applies during the official support plan until VFP becomes an officially "unsupported" product in 2015.
>
>You may never see an official announcement from Microsoft making a commitment to what I have just described (aside from any language you might find in the descriptions about the official support periods), but that was the answer given to the MVPs when we asked that specific question.
>
>From my perspective, this probably means that a distinction would be made between a future OS released during the official VFP support period that caused VFP9 apps not to run and perhaps just cosmetic problems with VFP9 taking advantage of the new OS's controls. That's just my speculation and not anything official.
>
>Suffice it to say that there are people inside Microsoft who are extremely interested in helping the community continue to use VFP effectively for years to come, and I believe they will do everything they can in the future to address any app-killing problems that might arise.
