If I were in MS and wanted to sneak VFP.Net under the radar, I would do 2 things: a) describe it as being for fledgling coders; and b) keep it as much out of the media as a I could. a) would get some buy-in, perhaps, from ScottGu; and while b) would help keep it out of the gunsights of the program managers who want to keep resources for their team by keeping them away from other teams with less political power.

If VFP is for fledgling coders, then with 30 years of xBase coding experience, I am a very experienced fledgling. So be it: I'm judged by my results, not a naive (not MJ's, but those who would disparage VFP as a conceptual base) judgment about the ability of VFP to produce production programs. Based on number and complexity of applications in use, VFP has nothing to prove, as you know.

>Hank, I guess I'm relying on MJ's reference to "visual" and "fledgling" coders. Seems to me that there would be few VFP fledglings in the First World and people taking up VFP elsewhere do it at least partially because it can be expected to work OK on customer machines and OS that may not have Aero or 8GB RAM. There's probably quite a few who feel that way in the First World too, but they're not fledglings. ;-)