>As Kevin, I too am tired of this discussion. This is my last comment. To you and JR.

That is your choice...

>First to you. This comment about "out of the BOX" is absurd at best on many levels.

It is not, because it outlines the capability of the tool. If you insist on using a framework providing certain functionality then you are not talking about the programming language but the framework and should insist in comparing frameworks rather than the programming tool. What you can do with framework X in .NET does not mean anything to any other .NET programmer who uses framework Y.

It really sounds like the argument I heard before that you can role your own data handling class that would implement local database engine SQL functionality. Well, go ahead.... Not a simmple task for a single developper. Maybe you can find a commercial solution ( $$ ) which likely will be a niche product with limited lifespan since .NETs data handling capabilities are evolving significantly by the year.

Again, you can build data driven applications in almost any programming language, even assembly if you like. The ease, scalability and performance of building this differ significantly accross tools.

Perry, I'm fine you're defending your choice for .NET, but ignoring VFPs technical advantage based on your non technical arguments (but rather on incidental personal observations) I find most silly.

>Not the least of which is 1) Development tools like are designed to require some work up front. VFP is also. Do you mean to tell me that every app you write in VFP, you start with a 100% clean slate. If you decide that you want to add a couple tools to your Java/dotnet toolbox, who cares? They will be there for this current project, and every project you do in the future. Another grasp at straws.

Of course I'm not starting blank. But tell me, if you would start blank, which tool would give you the best start ??? If VFP, then tell me what .NET add-ons do you use to be up to the same speed as with a comparable VFP project ?? What do you use to have the same functionality as EXECSCRIPT() ?? How do you handle late COM binding ?? How do you handle untyped datasets in your .NET applications ??