Hi Steve

>One caveate, all code has warts, and frameworks are no different. And sure as a user trys a new framework product, it is going to seem "broken" because it doesn't work like "I want it to". If you are going to use a framework, learn to work within the frameworks system. Discover its limitations, and work aronds. It will save you a ton of time, and make you money, Fight it and you will become frustrated, and unhappy. Framesworks, by their nature CANNOT be all things to all people.

I think this is a key issue to be successful with any framework, and I stumbled on to almost by accident: I was learning VFP and OOP at the same time I was learning MaxFrame and I figured that the best way to get quick and cheap support was to "never fight the framework". Fortunately Drew's defaults or approach fit very well with my wishes and preferences (wherever I had one) and the rest I was prepared to go along with and learn from. When we took the same approach with Visual Extend, we did not like the results at all; it was easier on us to switch to MaxFrame than to struggle with getting what we wanted using Extend.

So far we have had no regrets using MaxFrame.

Thanks for your input,

Reg