David F,

Thanks. I will try this too, and ask my users which solution they like better - actually, come to think of it I think your solution makes more sense - because a user would not normally think of clicking a disabled button, but they might drag the mouse over it for help - which solution is more consistent with Windows interface standards/guidelines?

To implement my solution with the command group I disabled the button itself but kept the command group enabled, and coded the status message in the click of the command group, and made the command group height and width slightly larger than the command button, with no border.

>David,
>
>Why not change the .ToolTip = 'Print is disabled for On Hold Orders' at the same time you set Enabled = .f.? Set the .ToolTip = "" when you set .Enabled = .t.
>
>You have to make sure you have the form.ShowTips = .t.
>
>>I disable a Print command button when a given condition exists on a particular record. But the user wants a message to pop up when they click on a disabled button - for example: 'Print is disabled for On Hold Orders'.
>>
>>Some alternatives are:
>>
>>1) Keep the button enabled - but disable the function - misleading because it looks like they can use the button
>>2) Return .f. from the when - misleading also because it looks like the button is enabled.
>>
>>If in fact no events fire upon clicking a disabled button - what workarounds are there, if any to accomplish this?