>I have determined that I don't like VMP.
>
>There is code in EVERYTHING!

Well. As I've said before every place I've seen VMP used, it was twisted by those who had it.

>
>I spent an hour trying to disable a command button. I set the Enabled property False - it
>came back on, it put This.Enabled = .F. in the Init - it came back on, form's Activate - it
>came back on, and Show - it came back on, and other places, and it wasn't until an hour into
>it when I found some obscure code down in the framework doing something with Refresh().

Bill Mason, I believe, told you earlier that you have to override certain buttons in the refresh().

>
>Right now I'm trying to run a stand alone form. I have been stepping through framework level
>code, and there is code all over the place doing things that seem really meaningless..

>
>The feeling I get is that my knowledge and experience in VFP is negated because I now have
>to learn new ways to do simple task all over again.
>
>The purpose of a framework should be to make my life easier, not more difficult.

I understand your frustration. I go through the same thing everytime I join another developer's project. :)

This is the same with almost everything. If you built your car by hand, you'd know where everything is. Yet, I'd curse you when it's hard to change the spark plugs. :) Nothing is truly Lego block easy in software.

There are extensive explanations of how to put stuff together in the zreadme and in several of the methods. Buttons like the Add, Save and Cancel buttons come with certain behaviors. If you want to stop them, you have to know how. You don't code their behaviors, that's already done.

Follow the directions in the zreadme for putting a form together. They work. Trying to trace all the code is like trying to dismantle the car to find out why it won't start.

http://vmpdiscussion.visionpace.com/