>It is MS (I'm not including the VFP team) that has become myopic and rather grandiose with respect to the needs of small to medium size businesses. VS is positioned as an ENTERPRISE development suite. Bottom line is that MS wants to play in the same sandbox as IBM and Oracle and win the support of the MIS oldtimers who, for years, have been laughing at MS with respect to database technologies. This is their target and I believe this to be the reason why they are downplaying VFP because of the stigmas - xBase, .dbfs, .cdxs, no native compiler, blah, blah, blah - all those things which were never robust enough for their needs, and rightly so.
>
Jeff,

I think your point is well made and I would like to add to it. <g>

I believe the ENTERPRISE problem with VFP is not the only the stigmas you mention but the lack of developers when compaired to VB, VC++, etc. People almost seem afraid in some instances to use VFP because they know so little about it and don't know any developers.

Also, the last two places I worked for were real big on setting "standard tools" to be used for internal developments. They both sanctioned VB and looked at me like I was crazy for using VFP for my own stuff. Never mind that I actually did stuff while they putzed (sp) around.

Scott