>If you're first project is going to be a HUGE application, taking the traing class might be helpful. I had the good fortune to be able to play with the framework for several small applications before having to really do any work in it. I might have gotten frustrated if I jumped right into a big project with it. That's not to say the framework is "hard" to use - I can crank out some really nice looking forms in a very short amount of time - but originally it took a bit a relearning to get my mind around how things worked.

The framework is not hard to use. But it does have a fairly high learning curve (takes time to lear), if you are not expert at OO stuff. It took me three weeks to get my first form out with the thing -- but after that I cranked them out at a the rate of one (highly complex) form every couple of days. As with any framework, you need to evaluate what it makes easier and what it makes harder and decide whether it is the framework that suits your application.

In the company I'm in now -- we do large batch applicatons -- very little interface, a whole lot of procedural processing -- a lot of intense stuff done to very simple data structures. MM did not seem the right framework for that so I'm not using here. But in any application that has a lot of data entry, or a lot of querying or a lot of reporting (in short just about any application other than the kind we have at my current company) I think MM is the best. Also I like its business object model -- best multi-tier in VFP in my opinion.