Hilmar,

I always have the example of the installing of the older versions of Novell, where Menu-options appear when they are applicable to previous choices, or just are not there because of that. Nothing is more anoying than looking for your option, being sure it's somewhere there and appearently related to some previous selection someweher. IOW, I hate that. Therefore I would always disable the button (and have it visible), so the user can see that it is there, but not applicable for ... the thing you can define in the ToolTip.

Of course you do this only in this way when this one user is able to have the button enables and visible at any time (not matter how rare that would be);
I would say, that even if he is not authorized for it and will never be able to use it, he is still allowed to see it (she too). This, because he can have seen the button by a neighbour, and starts looking for it again.
Only when a system-wide parameter says the button should not be used, then it should be invisible (always for that system).

HTH

>When a command button (or other object) doesn't apply in a certain situation, I can either make .Visible = .F., or .Enabled = .F. In general, what would be better UI? Any opinions?
>
>Hilmar.