Jim, thanks for responding, and I like your logic on this issue. If I apply your premise that a button's purpose is to allow communication with the system, shouldn't an accidental push of the button be handled by the button with a decision prompt like: if messagebox("Continue",33,"Continuing will cause x")=1 and its endif wrapped around the method call? I mean rather than pollute our method with such code? < TIA >

>>Hi Terry ---
>>
>>It belongs in the command button. The separate object communicates it's end status to the button which relates the status. If there is a wide range of outcomes, consider a messenger which would communicate the text of the outcome to the button.
>
>John
>
>I disagree, the button is strictly responsible for providing a mechanism for the user to communicate with the system. The button should do absolutely nothing but fire some other method of some other object. The use of a message object to handle display is a matter of design and it could be used or the process method could do the messaging.