>>I continue to strongly believe that the perceived differences between the two technologies is based on a 'mom and pop' model that is becoming increasingly marginal.

The presented differences often do seem to rely on the misconception that VFP is best suited to or can deliver only a "mom and pop" model. Perhaps this assumption is inevitable if people never had the opportunity to do a big system in VFP, and are exposed to the scalability features in dotNET. I use the word "perhaps" to show that this is suggestion to explain a visible phenomenon, it is not an attack.

For me, presence of a local data engine makes a significant difference to the big systems I've been involved in since 1995. Yes, I know about the workarounds, including SP that certainly makes a difference in some cases. But we've got US Patents in some areas that are only feasible if you can manage giant datasets locally. It is possible in dotNET, but it is stupid. Just as creating a comms component using VFP would be stupid. There is room for both realities in real life.

For me, I'm happy to live with the faintly superior attitude exhibited by many dotNET people. But when I see concerted onslaughts against VFP, I feel constrained to reply to the FUD in my own purely selfish interests- until dotNET gets smart with local data, I can't afford to see VFP consigned to the basket-case corner. And I'm not alone.