You're right!

>>Must be for very simple requirements. I remember this shop did layouts in PowerPoint, regardless of business rules and optimization, and then fit processes and structures to the screen layout, kind of a function follows form method, rather than the optimal form follows function. Of course this was an in house project, not a commercial venture by any stretch. 1 or 2 good VFP people, without a frame work, could have delivered a faster, more robust totally optimized solution in less time than the 20 bench programmers took using the framework.
>>
>>But MIS managers need someone and something to manage and the HELP desk needs someone to help.
>
>Uh, that's not a framework. That is a poor design approach, but it is not a framework.
>A good framework is a system of classes and procedures that can be used to perform the most common actions in a database application, such as adding, editing, deleting, flexible validation design (which allows for the custom validation that will be required), flexible error handling design (which allows for the custom error handling that will be required), etc., no matter what customizations maybe required.
>
>I've also found, time and time again, that a solid framework will help limit the management and help desk calls to the specifics of the application.