>Hi,
>
>I would like to bring one more point into the discussion, Marcus started with his thread. It's the question of extending the basic functionality of the MM base controls.
>
>Here's an example: I would like to have code in the base textbox, edit box and combobox, that prevents the user to get out of the control with "backspace".
>
>If I want to have that behavior in the MM forms, I have to put the code in the MM framework base control classes. Not a good way, but IMO no other possibility, besides not using the FW forms under cBizObjForm.
>
>Ok, I'm not using the MM forms now, but I want to use the control containers. So I can put the code in a subclass of the containers. That's ok.
>
>But if I want to use the control itself sometimes, I again have no other possibility than putting the code in the FW base controls.
>
>My conclusions: If I want to have basic behaviour changes in controls ...
>
>1) I cannot use the MM forms under cBizObjForm and I have to decide, if I want to use the control containers everywhere or nowhere.
>
>- or -
>
>2) I have to put my own code in the MM control classes and will have a lot of work, when the FW is updated.
>
>Wouldn't an intermediate layer in the framework be usefull here? Or any other predefined places where I can put my code (e.g. Hook-Objects)?
>
>Any comments and suggestions welcome!

Kevin is always open to suggested improvements, so sending him your code to do this is likely to see it released into future versions of the framework. (Though possibly with an added lAllowBackspaceOut to turn the behavior on/off.)

New versions of the framework always come with a 'What's New' document that lists the changes, which should make it very easy for you to ensure that your work isn't affected by the new release.

So, in short - go ahead and make changes to the MM controls to make them work the way you want them to.