Hi Gar,

>For me the perfect compromise would be a library -- sort of Stonefield on steroids, or a version of Mere Mortals where the utilities and objects were much more loosely coupled and independent of one another. Don't know if there is enough demand to justify a commercial developer coming up with something of this sort -- but I supspect if it existed some of us would use it.

Having had developed my own framework, I can say how difficult it would be to achieve what you are suggesting. One way it could work would be to create some sort of framework consortium and achieve a consensus on component interfaces and behaviors. Components could then be swapped and it wouldn't matter who developed the component(s) as long as they abide by the standards. Actually, this could be a boon to the VFP community.

>... but the Framework was actually quite suitable to the project. The developer had simply never bothered to learn Foxpro, and thus could not use any of the hooks to attach custom code! Obviously an example of how not to do use a Framework.

And an example of the type of developer never to hire.