>>Going back to the old rumour about non-support - what exactly gave someone the "impression" in the first place, to start his rumour?
>
>Jumping in a bit late ...
>
>My boss, who is generally a pretty canny guy, decided that VFP's days were numbered when MS announced that VFP was out of .NET
>
>We're expecting that within about 2 years we will be using something else.
>
>A big pity since we have moved from thick client to thin client/distributed processing just as MS moves VFP back from the middle tier to the front :(
>
>Les

Sometimes even the canny
Make decisions more akin to the fanny

You are right - it is a pity, especially given the "reception" that .NET is getting GENERALLY.
There are still far too many people running (and developing) FPD/FPW apps. to permit MS to remove much of the backward compatibility code from VFP. And this person is going to move away because VFP's stopover (it was a single version, after all) in the VS box has ended?!?!?! (while admitting that I would still prefer it in the box because of the cost perspective, but I'm a solo developer).

Regards,

JimN