Rodney,
A framework tries to anticipate all the problems you could run into. You may never have a given problem or you may run into it all the time. If you're making a simple program to be used by you alone, then most of the framework functionality is merely overhead to slow the program. If you're writing a distributed n-tier application for international use you'll find the framework has thought of (and hopefully solved) problems you hadn't dreamed could exist.

The basic classes included by most people are subclasses of the base controls. On your 2 forms, what if your boss/client suddenly wants every textbox background to be bright green? Sure it's easy to go through 2 forms and replace 15-20 control properties. But what if you had 40 forms? Subclassing then becomes a lifesaver.

Also, if you have a function that is used in more than one form it makes sense to add it to a class. The class is then dropped on any form when needed.

HTH
Barbara

>I'm just wondering about the popular opinion of AppWizard. It creates a ready made "framework", but is all the stuff it generates really necessary?
>
>To simplify my question, if you create the database, a couple of forms, a menu, a report, and a main.prg, and then make an executable out of them, are you asking for trouble?
>
>Further -- I'm experimenting with the k.i.s.s. method and am to the compiling stage. I noticed that there was NOTHING in the class pageframe of my project manager. Is that necessarily a bad thing?
>
>Rodney