You have to mean a RAD tool, not a framework right?

>Terry, that is a very unfair and unrealistic comment. I only venture in here to set the message straight to any potential new VFP developers out there who may mistakenly understand your statement to mean that only unskilled developers would use a framework. I hope that was not the message you intended to convey...
>
>Well it was the message I intended to publish.
>
>I can tell what framework was used for Quasi VFP projects just by looking at the screen and observing the behavior. They're sluggish, fat (I saw a single form FW demo with just a few textboxes that compiled to a 2MB exe!) They're nothing more than glamorized "form wizards"!:)
>
>When a framework is used - it is not a VFP project. It is a framework project.
>
>Recruiters have asked me to work on framework projects. Several in NYC - they call them "projects in trouble". All I ask - is that those developers that use frameworks do not claim they are VFP projects - they are just an [another] easier way to slam low quality grids on a page frame and, providing the user is brain dead enough, call them a program.
>
>Frameworks are just as bad for VFP's image as the old-time VFP browse window consultants' work product.
>
>We don't need frameworks for VFP development - unless, off course, we honestly admit we are little more than spread sheet template clerks pretending to be VFP developers.
>
>I'll put anything I have (or can do) up against a "framework" project anytime and will blow it's huevos out of the park!
>
>There are no short cuts to quaility project development - period. You can't learn the power of VFP hiding behind a form wizard!
>
>Am I clearer now?:-)