Ryan,

>Delete and New Windows Forms buttons are standard in the framework, but it doesn't appear that there is an Edit button. I would assume this is because your standard MM interface dictates putting the list/grid on the same form as the editing controls, just on different pages.

Actually, there IS no standard MM interface! I've put some samples together that demonstrate one way of putting an interface together, but in MM .NET (as is the case with MM VFP), we don't force a particular "look and feel" for end user applications. If there's one thing developers want flexibility with, it's the UI. That's why we've provided the mmBusinessForm base class that has all the behind-the-scenes functionality you need, but is otherwise a "blank slate".

>However, suppose I want an Edit button that calls another form for editing. What is the best-practice for doing so? Would it be to subclass mmButtonBehavior (adding logic for controlling Enabled state, etc), or is there another way preferred by the framework that I'm missing?

You can definitely subclass the mmButtonBehavior class if you need the enabled/disabled functionality for a custom edit button.

Regards,