>>Let me take the opportunity to say I'm abivalent about a switch to turn it off. It's not something that causes me a problem, and, if I had a choice, I'd just as soon work be done in other areas. If someone else thinks it's a good idea, I've no problem with that.
>
>I'm with you - no need to turn it off, just give me an inkling what it's looking for. I've only had it once in a user app in recent history, and it was devastating to the user. "Cancel" was the wrong choice ;-) I get it often enough developing that giving me the file name is more than enough to fix the problem. Just fill the structure for me!

OK - launch fox, and type "skip". You get this dialogue. Not even you, as a programmer, would know which table was this supposed to be in, if it so happened that you had such a command in a general practice routine (like oTable.Next() or so). In most of the situations it simply can't give you any good hint at which table was it supposed to be - but having an error you could catch (instead of the dialogue) would make more sense, IMO.

What's this, I'm running a campaign? I'd better go to sleep. :)