Hiya Jim ----

OK....it could go both ways....what if the processing object is a DLL that can't expose a UI? If the outcomes are simple, then a DO CASE in the button after a value return can show a message....




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

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