>Without getting too dramatic about it, a framework is just a component. Larger-grained, perhaps, than a UI control component, but a component nonetheless. Large-grained components cost more, require more investment in time and learning, and have a correspondingly larger payback than little components, especially on large projects.
>
>Nobody should recommend to not use components where clearly appropriate.
>
>And please, learning VFP is not a good reason to write your own framework. The best way to learn VFP is, by far, to reverse engineer several existing frameworks and learn a few of the million ways you can model any particular situation.
>
>In my 2.6 days, when I was using CodeBook quite a lot, I made a number of fundamental changes to the architecture that were right for me. Because I shared a lot of what I did, many others benefitted, as I did with the many others who shared with me.
>
>In my VFP moments I've used VMP, Codebook, and CMM, and I've been paid to take a long evaluative look and write recommendations about using these as well as IAS ObjectTalk, Visual FoxExpress, Visual Fox Extend, and Promatrix.
>

>All of these are excellent and getting better. Not perfect for all (or even most) situations obviously, but hey, I've seen accounting systems written in Word macros which goes to show that meeting immediate requirements is usually possible no matter what you use.
>
>Of course you can write your own framework. Many of my best buds have done it. It's an iterative refactoring activity that may make sense if you will be writing many applications with it, and you can afford to evolve it.
>
>I work for hire for customers. When we start something new, I always recommend a commercial framework because someday I want to walk away. I want to walk away after hitting a huge home run, walk away tall, a hero. You can only do this if you use a commercial quality framework, and only if you use it well, and only if you leave people behind who can care for themselves.
>
>I've never seen a customer that was well served by a consultant who walked away leaving behind a half-cooked proprietary architecture. Remember, sooner or later, all consultants must walk away (or be hired full-time, which is definitely not my goal).

Even for the sake of argument, Frameworks are helpful in developing apps, but ohh my... how would you synchronize everything to make your apps a quality one? Different approach coming from a lot of above listed frameworks???

The issue here is using frameworks to develop fasterrrrrr end-user apps, and not only to get ideas out of it.