Kevin,

I think you are missing the whole framework idea. You cannot just walk into a new company with a whole new application that was written with a framework and just work like you always have. You need to read all of the VMP documentation and work through the tutorials that came with it if you want to reap the benefits. You are going to have weeks of learning to do before you can be productive at all. Once you have done this, then you can produce applications and add new features at an unbelievable pace. I am currently working learning C# and dotnet. It takes me 10 times longer to do anything than I would be able to the same thing with Maxframe.

You just have to give it some time to see why things are as they are. If you don't like certain features, you can always override them in your base classes and have it your way.

Bill


>>>>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.
>
>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.