John,

Honestly, you can't go wrong with either approach. It boils down to a question what fits your style best. For instance, before the last version, MM had almost no wizards. It then came out with a data driven wizard for creating bizobj's and GUI stuff. But the wizards are not all that strong. For some, that's a major drawback in a professional strength framework. It's strength lies completely in its superb object model and fast performance.

Also, when choosing a framework, you need to look at the object model closely. How is the framework accessing data. How scalable is it? Will it adapt easily to component based development? What kind of internet support does it provide? Many of these issues revolve around your personal preferences on programmimg and application design.

A good example is client server computing. I have never seen demonstable proof that using stored procedures is light years faster than using Remote Views, yet everything I've read and heard says stored procedures are faster. This may be true, but VFP's Remote Views are a great tool for seeing and updating client-server data. With a proper framework, I'd have options to use both models where appropriate. I would not want a framework that locked me into a certain methodology to tightly.

Best of luck.