Ok, if the "self-proclaimed NET gurus with little or no VFP experience who crashed and burned" statement is aimed at me then I take exception to that.

Oh boy. It's the scenario in the message to which you originally responded: Message #1298510 .

Yet I am being ostricized for daring to say it I don't believe it is the best tool for the job anymore.

Here we go again. Nobody is surprised or hurt if you don't believe it is the best tool for the job. No problems; we all find our success our own way. But you don't stop there. You also deliver slaps at "the majority" to whom you assign mythical beliefs defended with religious fervor. And then you open your eyes wide and pretend that it's your decisions that draw reaction rather than the gratuitous slaps you seem to attach every time.

Apologies if that opinion offends you but the entire stance baffles me.

Let me try again: you find NET as productive as VFP, or even more productive. Good for you! Other people share your experience. Good for them! Some people do not share your experience. Good for them? No, it seems that experience is only valid if it matches yours. Everybody else has something wrong with them.

I just don't see why people are so strongly opposed to the possibilty that better development platforms might be out there.

Do I really need to say it again? The strong opposition is coming from *your* direction, directed at people who have experienced something different from you. The only opposition to your preference for NET is invented by you so you can attribute it to others and shake your head. Give over.

Where a local cursor engine in VFP was nice I haved used objects to represent tables for years. Given this approach the plumbing for me in DotNet is just much cleaner. It allows me to write better code faster...

Interesting- that used to be said a lot until Anders Hejlsberg began promising more tightly coupled data within 5-10 years in NET, even referring to fox as an example of how it can be done. I prefer Anders' stance to yours- but hey, if the existing is better for you, that's cool with me too! it just means we're doing different stuff. Are you using LINQ yet, btw?