Great advice - thanks Gil.

Do you subclass just your forms, or other classes as well? It seems that there may be a number of situations in which one would want to enhance the MM classes (for example, in the automation classes), and sublcassing would keep the enhancements alive through subsequent MM versions.

>David,
>
>Alex gave great advice. I can only add a couple more:
>
>Be sure to keep a log of the framework specific errors caused by your mistakes and their solution. Most likely you'll make the same mistakes several times and having the log will help you correct it faster instead of re-debugging the exact same problem you made a month ago (but who can remember the details with so much other stuff under the bridge since then?)
>
>Download the 'Find Table In SQL View' utility found here on the UT. This allows you to quickly see all the views a table is found in (but the caveat is that at least one of the table's fields is marked as updateable even though you man not have it Send the updates. It uses dbGetProp which seems to filter by the logical Updateable. This utility is very handy in case you can't buy Stonefield's SDT right away since you'll be able to see all the views that could be broken should you modify a table.
>
>The code comments are just as good as the manual and Kevin heavily comments. Delving under the hood should be required reading.
>
>After taking Kevin's classes I jumped right in with a brand new project. I had not done anything of this magnitude in ANY OOP version of VFP before and considered myself a complete novice at OOP. I now have 2 large applications that are professional in appearance and functionality, both done in MM.
>
>I'm sure that more for others but If you practice GAPP (not to be confused with GAAP) Generally Accepted Programming Principles then you should do just fine. Microsoft Press has a book by Steve McConnell called 'Code Complete' that great for spreading this gospel. And Savannah Brentnall's 'Object Orientation In Visual FoxPro' is very good, especially good for beginners like me.
>
>For a particular project, if you find that you want your forms to have a particular look or feel, subclass them (following Kevin's guidelines) to your project's LIB folder and use them, the same with any controls.
>
>Keep your own common folder/sub-folders for utilities, etc.. that you've created/bought/downloaded/borrowed and add them to your path in Startmm.prg
>
>Well, that was more than a couple but I've always been longwinded.
>
>Happy Sailing!
>
>
>
>>I purchased MM a few weeks ago. I've read about 1/3 of the user's manual (which itself is worth the price of the framework). I'm very psyched to get going with it, but as with learning anything of this magnitude from scratch, I'm not sure when to stop reading and start doing, so I'd appreciate anybody's advice/experiences with this process.
>>
>>What did you do to learn the framework? What were the biggest mistakes you made? What pitfalls can you help me avoid? Did you just switch over 100%, or did you slowly make the switch? What big-picture concepts were you missing when you started, that you understand now?
>>
>>I'd really like to take Kevin's class, but it's not in the cards for the next few months at least.
>>
>>Thanks in advance for your thoughts!