>>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 >
>
>Terry,
>
>You could do that, but I hate those "Are you sure" messages. The suer must take some responibility for their actions. If the process is a potentially destructive one then the issue is different. The button should ahve no knowledge of the process that will result, so it doesn't know that it is potentially destructive. Only the process itself knows that information, so it should be the process that provides for a nondestructive out.

Thanks for responding on this as I needed to clear this up. I keep coming back to this question as I try to get my object methods specialized down to doing one thing well. I think what I need to get used to is having a setup method and a cleanup method in my objects for such things as I was tempted to put into the command button or such control. I can't wait until devcon where I can look at lots of frameworks. I will definitely be at one of your extending the framework talks.