Perhaps. Perhaps. It would be nice to benchmark it. We need somebody to put up some money. Then we compare the end [work] product - a VFP full cycle developer (and their attendent libraries), and a FrameWork coder.

Let's see: Money, 3 month project, VFP developer, FW coder, a requirement - then lets see whose got the jazz at the end of the project:-)

>Terry,
>
>>There are negatives associated with off the shelf frameworks. To many of us, understanding how the underlying architecture works is important. Commercial frameworks seem to have a tendacy to hide that from us. We become framework code scripters. To me that is a step down from programmer or developer.
>
>I agree with you to a point, but must say that studying the inner workings of a framework that comes with source code can be one of the best educational endeavors a developer can experience. Also, the best frameworks, in my opinion, are those that do not force you into one limited way of doing things, but give you building blocks and tools that speed you on your way.
>
>I have worked with frameworks and without and see both sides of your argument. However, I learned a ton of good programming practices from studying Rick Strahl's Web Connection framework and business object framework, Drew Speedie's Visual MaxFrame, and Kevin McNeish's Mere Mortals.
>
>So, properly used, a good framework can not only speed your development, but can help teach you the underlying technology (but only if you dig in and actually study the code and read the docs). BTW, I'll say again that Kevin's documentation in the freely downloadable Developer's Guide for Mere Mortals VFP and MM.NET are top of the line and WILL teach you if you let them.