I just downloaded Toad 13.1. How can I disable the annoying pop-up error windows? I don’t want to be constantly told I can search the Knowledgebase and forums for a solution.
The error dialog happens to have the “search knowledge base” option, but we shouldn’t just be showing that dialog willy-nilly. There should be a good reason that the error dialog is showing in the first place. If you don’t think there is, let us know what the error message is and how to reproduce it, if possible.
Thank you for the response.
The dialog shows when I have an error in my SQL code. I am able to diagnose the error without having to have a constant reminder from the error dialog window. The knowledge base would not help when I have a complex SQL syntax or logic error anyway. There should be an option to turn off the display of the error dialog, but keep the blue highlighted errors message available.
The KB button there is in addition to the ORA error. The dialog would still be there for your ORA errors regardless of any supplemental features it includes. Don’t code errors and you won’t get error dialog. 
The dialog underwent a bit of a cosmetic change for 13.1, but it is not new. If you are seeing an error dialog now where none was present before please provide steps to reproduce.
Thanks,
Michael
For comparison here is the dialog in 13.0.
And the dialog for the same error in 13.1.
The new uses standard Windows Task Dialog now whereas the old was a custom Toad window. In addition to presenting the same info using a dialog more closely following Windows style guidelines, it fixes other bugs like this gem. In trying to get screenshots my 13.0 dialog got stuck in Stay on Top mode and is now in my face on top of all other applications even when Toad does not have focus.
I concur with the example popups provided; however, the 13.1 popup is so much more pronounced that it is annoying. I prefer the simpler, direct oracle error message that is in 13 popup. I believe most experienced users will know to click on ‘Help’ to get to toad specific resources. My preference is to include the Knowledge Base portal under ‘Help’.
1 Like
If you are a beta user check next beta (13.2.0.11 or newer). A few changes have been made so that the KB button is a little more relevant.
I'm also looking for a way to disable the popup when there is an ORA error. The error showing in the message window is sufficient. I don't need a popup that requires me to close the window every time I have a syntax error or mistype a table name.
2 Likes
For me too it is enough looking at the message window. Do not need any KB-Help when I make little mistakes like wrong column_name or forgetting quotation mark.
Very annoying !
And yet no-one has directly answered the question. I'm new to Toad and this, this is enough to make me use something else if it can't be turned off. Why do I have to dismiss a modal dialog when the message is already written to the messages pane? I'm sure that if I got as far as getting Toad installed, setting up connections and was querying a database, I could figure out how to query a knowledgebase if I really needed to know something about an error without having the 'helpful' dialog present me with a button.
So the question remains - is there a way to disable this dialog? If not, is there a community idea or RFE open to provide users with the ability to disable the dialog that we would vote up?
1 Like
OK, here's a direct answer: We don't have plans to remove the error dialog.
I sympathize with you, but all you have to do is hit ESC and it goes away. Although it changed recently, it's been in Toad since the beginning, so if we remove it for you, surely other users will be annoyed.
So why don't we just add an option? Toad is a big product with lots of options already. We have heard a lot of criticism about how complicated it is, etc, etc, so we're trying to not add options every time there is a suggestion. In fact, we've been trying to take some options away lately in an effort to simplify.
That's not to say this will never happen. But so far, it seems like only you and 2 other users are in favor of this. If you want to start a movement to have it removed, we have the "idea pond" for stuff like that: Idea Pond - Toad World® Forums. Add an idea, get your coworkers to vote on it. Don't give up!
1 Like
I also find this error popup very annoying and have been searching for the option to switch it off. An option to do this would be valuable. We are intelligent enough to cope with the options 
keep em coming.
Vote
JohnDorlonQuest statement, sounds quite a bit like complete ignorance to customer needs:
OK, here's a direct answer: We don't have plans to remove the error dialog.
Nonetheless he offered to open an Idea-issue. I did just that:
Please remove annoying Annoying Error popup and gong on every sql error
Please upvote.
This has to change or TOAD will loose are frequent user/customer.
Regards
OL
@othmar.lippuner My statement was not an official Quest position on keeping or removing the popup. I am one of the Toad developers. All I meant is to say that we have not made plans to remove it, and I said that only because someone implied that we were dodging the question.
Hi John Dorlon,
Sorry, my statement may be was a bit direct.
Still hope me feedback helps you to promote a frequent TOAD-users view in development. Also hope the started Idea get’s enough upvotes.
I just recently switched to newest TOAD-Version. The first few days I’m tolerante for such changes in behaviours, may not even notice it consiously.
After a while I noticed, then it starts sucking, start searching to turn the nuissance off. Not be able to turn off an anoying feature is a nogo.
Further when working with SQL I don’t need access to a knowledge database. When working with complex SQL a developer has to handle with a few hundreds of column names and these are changing constantly oft he day and weeks with each shift in work area. Typos, bad name guessing etc. are 95%+ of all these errors. They are eliminated on the fly. Really don’t need a bell and a popup to discipline me, the more these little errors don’t go away, every little change can bring new ones, now an then. Should that popup offer help or should educate the user to do better? Both attempts are completly in vain.
All the 30 years I’m programming I use the compiler or parser to help me to quickly get rid off little naming mismatch etc. That’s the normal way to use any IDE. An IDE should help an coder, this is ment to be computer assisted coding. Computer assistance is meant to be support in coding and this should be done at the lowest possible intrusion level possible. An error message should minimal invasive. Popup’s are very invasive, bells even more.
I remember when coding in Microsoft VBA editor there is a similar behaviour as a default. It sucks as well. By the way, It can be turned off.
Fort he 1% or less of errors that need a bit more of thinking, or even need consulting the web and other knowledge bases, it is not worth hitting the bell and poppers a 100 times.
Just another idea:
Think the message view with included error subview is part of TOAD one page application GUI (each popup breaks this).
If there an error it is signaled in the error-message view. Anyhow if the view is not visible, things get a bit more difficult. Guess there is only an error in the bottom statusline.
Better than a popup would be this: Error-Message view is made visible automatically, or there is a single, ontime popup that ask if the message window should be made visible.
Have a nice weekend and week’s start.
Kind regards
Othmar
Hi @othmar.lippuner that's OK, no need to apologize.
@m.schouppe @gary.wilson @eddie.brettingham @leif.schmidt @WaterGirl
We'll add an option to not display the popup. This will be available in beta soon, most likely a week from today.