>>Yep exactly. WHY it didn't sell is a whole different thing. Plus I think it must be hard for MS to even know how many people were actually using it. Lot of developers got VFP with MSDN subscription or as part of dev studio - so maybe no one used VFP as part of dev studio - maybe some did - but no real way to tell. VFP was always different animal than rest of dev studio - the controls for the screens are all different than all the others and the way it paints forms etc etc etc. It just didn't fit in with everything else so of course they had to give it the ax. X-Base environment was dying prior to death of VFP too so all these things together and it's just not worth it to MS to keep it alive.
>
>I've never really followed this whole VFP debate but weren't MS intending to include VFP as a supported .NET language - and the idea was rejected by the VFP community ?

We were given a false choice. They said we'd lose internal database engine, the IDE GUI would be that of VS etc. OTOH, if we chose to stay out of VS, we'd never have 64 bit version (built now by that guy in China, partially built by eTecnologia), the tables will never cross the 2GB (done by eTecnologia) and a few other lies.

The whole thing was rigged, and I'd hazard to guess that if we didn't make the desired choice, there'd be people who'd become vocal in swaying the opinion in the designated direction.