Fumei, that looks to me like you're spamming. We'll have to report you to the administrators.

Why do you think hitting the Red X is an ungraceful way to exit a userform? The Red X is ubiquitous in the Microsoft environment, and anyone with a computer generally knows that clicking a Red X is a "get me out of here" function. If we could *hide* the Red X in Word VBA (the way you can in Access, if I recall correctly), I could go along with hiding it, but since we can't hide it... I'd rather not have a button which simple appears not to work over programming it to work the way a user would expect it to work (do *something* rather than *nothing*).

My philosophical approach to User Interface design is to, whenever possible, approximate the functionality and design of built-in microsoft dialogs. And the two most basic userforms I come back to are the Format Paragraph dialog (a modal form) and the Insert Cross References dialog (a modeless form). I also like the Find dialog in its approach to the "More" button concept (turning a simple form into a complex form for some uses).

The more similar a custom userform is to a built-in dialog, in terms of functionality, the less you have to explain to a trained user (and untrained users will need the explanation anyway-- with the added bonus that if they learn the custom dialog, then they will be closer to knowing how built-in dialogs work). And even though we can tell users not to click on the Red X, they will still do it... if only because we may not have an opportunity to "train" them away from this behavior.

And thus my argument has always been that a visible Red X should always work just like a Cancel button. But either making it work like a Cancel button or disabling it still requires custom coding (by putting code for the QueryClose event).

What is your argument for disabling the functionality of it? Habit? Or something more?