>>Isn't that sweet?... in the VFP forum, no less!
>
>>What gave you the urge to share this?... In such a friendly way??????
>
>Not trying to be rude, just honest. I have used VFP a ton and have many apps in production with it, not bashing it at all or its fans. I am just saying it isn't the best tool for the job anymore unless that job is creating a .dbf file.

PMFJI,

I’ve used VFP since version 2.0 (12 years of fox development), and I have been using C#.Net as a database development tool for more than 4 years now, but still to me development in .Net is still 20% to 30% slower than in VFP at least using VS2005. We’re just trying to explore VS2008 with the LINQ feature so I can’t still give an honest comparison. Ofcourse, the look and feel (UI) in VFP is ugly as compare to .NET but remove the UI factor, let’s say SPEED wise?? My hands down on VFP still. The builtin reporting engine is a big factor IMHO. In fact, just recently, somebody asked me to do an application with 20 db tables only using SQL Server and the timeframe is very short (6 weeks). Know what? I’ll do it in VFP – easy deployment less hassle.

So good thing MS didn’t include VFP to compile into .NET because the RAD factor will surely suffer. VFP is still the best tool for the job if it is purely DB devt, UI is not an issue, and you’re running out of time. Just my 2 cents opinion.