>You might consider putting the operational code that you have in the .Click event into a method that's scoped to the form itself. That way the functionality will be available to any control or process that needs it, regardless of the condition of the command button.
>
>Regards,
>Thom C.
You can activate a button's (or other object's) methods, even if the button is invisible or disabled. It is only the user that can't click on it.
However, I still think it is preferable - for organizational reasons - to transfer commands to form-level methods.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
