My opinion is that commercial FWs narrow the robust paradigm VFP offers. Solutions have to be taylored to fit the FW box. Ever notice how all FW apps look the same? Kind of Steppford framework syndrome. I think most commercial FWs promote weak design strategies. A novice can whip a screen out quickly, but the solutions usually have a lot of pushed modal forms and look like college projects. Nothing is better for our carrers or customers, than knowing how to design and develop a system that meets 'your' engineering standards. Commercial frameworks, may blunt the imagagination and creativity that seems so essential. Systems development is more art than science. Would Picasso have used a robot to paint?

There is more to system development than simply populating controls. Normalise and Optimise and have fun with the moment of magic life has given you!

DID I REALLY SAY THAT? Hey its friday.

>Does anyone have any opinion about whether or not the Application Framework (built into VFP 6) is worth using?
>
>For app devevlopment using past versions of VFP, I have used my own "frameworks" - mainly because the Application Wizards were so buggy and overly complicated. Nothing fancy, but at least I knew what was in there (and that I understood my own class libraries well enough to fix any bugs).
>
>We are now considering purchasing a framework (Visual MaxFrame), but until we get up and running with it, I'm wondering if it is even worth bothering with the VFP 6 Application Framework (i.e. would it be better to build with my own "framework" or no framework and then at a later time integrate my code into Visual MaxFrame as much as possible)?
>
>My initial impression is that the new VFP 6 Application Framework is structured somewhat better than the ones in previous versions, but that it is still overly complicated - not to mention poorly documented.
>
>Any thoughts on this subject would be much appreciated. Thanks in advance .....