>>>>Bill Mason, I believe, told you earlier that you have to override certain buttons in the refresh().
>
>My point is that I shouldn't have to override buttons. What you're saying is that I have to do something
>to overcome code that someone else wrote which is already overriding the default behavior.
>
>Why would anyone developing a framework alter the way the Enabled property works?? Now it's no longer
>intuitive without either searching a help file or by plowing through mountains of code someone else wrote.

Intuitive is only what you've learned.

>
>I don't know VMP well enough to make any extensive judgements, but when I have to jump through hoops to
>do something simple, something that used to be a simple mouse click in the prop sheet, it doesn't give me
>me a warm fuzzy feeling.

The point I'm trying to make is this: There are specific features most USERS want. For example, buttons that are tied to the mode of the form, Add/Edit mode should have save/cancel enabled, Default mode should have add enabled and save/cancel disabled. You will have to overcome this if you don't want that behavior. The point to a framework is to provide those desirable services to developers for the users.

I used to teach development teams how to use VMP. We spent a week after they had gone through the tutorials. I'd guess two weeks would be required to see all the stuff. I advise against that. I personally focus only on frmDEGridNav2Pages and use it for much more of my applications than most VMP developers. Less to learn that way.

HTH