AFAIK Microsoft didn't write the fix -- they took the hacker's work and made it available on their website. Which is nice, but not their original fix... I shudder to think what would have happened if the problems was somewhere real deep in the bitwell, too far for even hacker's to reach without a good roadmap to the guts of the runtime, if you will.

Pertti


>>>>> Well I'd expect MS will release a SP or hotfix for every new OS that
>>>>> causes VFP to have serious issues, at least until 2015 or so.
>>>
>>>No, that is not correct. Standard support only goes through 2009 (or January 12th of 2010 or something like that). In theory, Microsoft can issue fixes until then (although I would be somewhat surprised if they did), but during the extended phase (which goes to 2015) no service packs are released. Only security fixes, which VFP is very very unlikely to have.
>>
>>Can you back that up?? I cannot imagine that after 2009 if some serious issue pops up in VFP9 on a new OS, MS would not fix it. Like happened with FPW 2.6 where there were some issues with 'fast pentiums'. They eventually posted a fix for that. There are so many VFP applications out there that there would be a tremendous pressure on MS to fix the issue. I agree less serious issues would probably go unfixed, but I can't believe they would let all VFP applications die after 2009.
>>
>>Walter,
>
>I used the fix for FPW 2.6. I got it from a 3rd party who apparently had reverse engineered FPW, found the problem, and fixed it. He released a PRG file that took the foxprow and fpw2600.esl files and patched them. If I remember correctly Microsoft put a link from their Knowledge Base to the 3rd party patch. I don't think Microsoft ever did anything to fix it.
>
>Does anyone know if Microsoft ever released an official patch? I quit checking back once I had a solution.