How many copies of Toad would you want to have open at a time?
I easily spend 90% of my work day in Toad writing and running queries and pl/sql. I also use the Session and Schema Browsers on a regular basis. I can easily do everything I need to with a single copy of Toad open without having to wait on queries to do other things. I use the "execute queries in threads" option and sometimes have as many as 4 queries running at the same time in different tabs and sometimes different editor windows and I pretty consistently have at least 10 tabs and/or windows open.
The only time I open a second copy of Toad (usually the Beta and the GA), is when I need to compare data grids with lots of rows and columns side by side so I can use two monitors to do it or if I have somehow managed to lock it up and need to kill my own session. But the number of times I need to do this per month that could be counted on one hand. 
After all these years (I've been using Toad for 20+ years), I've found that if there is something I don't like in Toad, there is probably an option to fix/change that behavior.
On Tue, Nov 1, 2016 at 3:12 PM, Gregory Liss bounce-GTDG@toadworld.com wrote:
RE: Multiple Copies of Toad ( v12.0.0.61)
Reply by Gregory Liss
There are also numerous ways around this issue. Specifically the /Virtual flag. One reason that it was difficult is because of the thousands of extra features that Toad has that many other programs do not. Specifically, the automatic saving of your settings x number of minutes. Most programs do not have this but Toad does (requested by users) and this can cause issues if you have multiple instances open because you're saving to the same location. We've also solved this issue with the /virtual command line parameter but it was introduced in 12.7. Since you're running a version that is several years old, it's very possible you don't know about the changes and enhancements that have occurred.
Also, are you running queries in threads (an option)?
Are you running things as a scrip (F5)t? If so, we have to wait for the script to complete before returning control. If you have a long running script, execute via QSR or SQL*Plus to get control back.
Have you looked at connection colors to keep track of what is dev and what is prod?
Also remember that Toad was designed a very long time ago when MDI was the way. We have looked at alternatives but given the user base and the effort required, it's not really a viable option. Look at the nightmare M$ created for themselves when they redesigned Office to have ribbons. They can get over it because they have infinite resources and a monopoly on the space. Most companies simply can not toss their app into the garbage heap and start over. We're constantly trying to improve and will continue to improve things but posting an insult ridden tirade on a three year old post is not helpful at all.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or Unsubscribe from Toad for Oracle Forum notifications altogether.
Toad for Oracle - Discussion Forum
Flag this post as spam/abuse.
--
Phyllis Helton
Data Magician
Digital Products & Strategies, Cru | Data Sciences & Analytics
Office
407-515-4452
phyllis.helton@cru.org
