This thread got my attention for two reasons;First, it shows me the "right" type of discussion that needs to take place on web forums or newsgroups.... not just a technical support process (how do I do A? You do this...) but instead an opportunity to learn better ways of doing things. This was a pretty standard question, and most people (myself included on most days) usually just focus on answering the question. Instead of the fairly helpful response that solves their problem, what I think we all should do whenever we see a post on a message board is take a step back and try to determine if we can add more value by discussing alternatives... I have the best discussions when my first reply is "Ok, you can do that using blah, blah... but can you tell me why you want to?"Second, I just liked the response... why punish the user for their "bad" entry... disable buttons and menu options that are not appropriate, don't yell at them for pressing the wrong button at the wrong time (and worse yet, don't crash because they clicked save when they should have clicked Save As...). That is certainly a guideline that deserves a top place when you are designing and/or reviewing your User Interface. Like I said at the start of this post, I realize this is already a well-known UI guideline, but it certainly seems to have been missed in quite a few of the products I use.