In my opinion, buying a third-party framework is the way to go. I haven't used the one that comes with VFP, but when you buy a third-party framework you usually get a lot of support.

There have been several recent articles in FoxTalk (http://www.foxtalknewsletter.com/) about some of the popular third-party frameworks for VFP. You might want to take a look at them.

If you are going to Milwaukee in November for the Great Lakes Great Database Workshop (http://www.hentzenwerke.com/conference/glgdw_main.htm) make sure you go to the Framework Round Up.

Also, there is a new book comming out building your own framework in VFP.


>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 .....