Actually, all kidding aside, VFP and .NET, with SQL Server, are my calling cards...here are my 'general' rules

1) If the choice is mine, and if the client has decent hardware, I'll generally use .NET and MSDE/SQL Server. (though once I had to use .NET with VFP tables...long story)

2) If the choice is mine but the client has hardware that's below the rqmts for the .NET framework, I'll use Fox. (Haven't had that happen lately, but you never know...)

3) If the client insists on one or the other (they have time and $$$ invested in an app written with a particular tool, and don't wish to change), then I'll go with what the client wants.

Contrary to certain opinions, I've never said anything negative about Fox as a tool. It's a great product. I've used Fox since 1988, and have experienced the product's rich history.

But the fact remains that Fox is generally on a downward trend. I saw the trend a few years ago towards other tools, and invested large sums of time to become generally as productive in .NET. That has paid off for me professionally.

There's no question that one must write some code in .NET to do some of the same things one can more-or-less do in VFP 'out of the box'. The two are different paradigms, with .NET being comparatively more 'code-centric'. But I also find the .NET architecture to be comparatively more 'open-ended'. I also find some of the statements on this forum regarding .NET to be rather uninformed.

Just like my father, a former IBM and EDS stalwart, used to say to me..."he who has the most options wins".

Kevin