Steven,

I'm sure that you are correct in your assertions here.

But. . . Relatively speaking, VFP is still quite "new", and certainly the frameworks currently on the market all were initially delivered shortly after the announcement of VFP 3.

VFP 5 had some enhancements and VFP 6 promises more. Seems to me that there is a legitimate argument for letting the 'base product' STABILIZE *before* jumping onto the framework bandwagon.
Maybe VFP 6 would be the one, I don't know.

In the meantime, there can be nothing intrinsically wrong with learning the language the hard(er) way, including some semblances of a 'framework'. Sure, it may take extra time, but that time should come back handily in the end, over and over again.

Cheers,

Jim N

>Berofe you think the issues are, I recommend you review three things.
>
>The first is an overview of the economics of framework development which is excellentlt covered in the February '98 issue of Software Development magazine.
>
>The second is an article titled Leveragong Object-Oriented Frameworks at http://www.taligent.com
>
>The third is a paper called Evolving Frameworks - A Pattern Language for Developing Object-Oriented Frameworks at http://st-www.cs.uiuc.edu/users/droberts/evolve.html.
>
>The issue is deeper than you imagine, I suspect.