>My war story: I developed some interfaces for a local shop. The "Save" button remained disabled until the contents of the entry controls were changed. The PL, a carreer IT employee, wined it would confuse the user. My position was: If nothing has changed - there is nothing to save. My middle ground was to enable the "Save". But, data would only write if a change had occurred. IOW - It looked like the PL's requirement, but behaved efficiently, like I wanted.
>
>Moral: The ability to click a button that does nothing is more important (in dinosaur engineering) than not having the ability to click a button that does nothing <bg>.

I do the same thing (disable buttons). I've seen too many people talking idly on the phone and mindlessly banging away on a button for something to do, and in the process saturating the network with "do nothing" saves.