Since Toad is only able to use one client to make all connections within one instance of Toad, if more than one connection in Toad is established, the second connection will be forced to use the same client that was used for the first client. This is fine. The problem is that when the second connection is made, if it is with a client other than the one that is set as the default in the connection window's grid then the client gets updated as that connections new default client. This should not happen. It should connect with the client that is currently being used, but the default client should not be updated.
WORKAROUND:
None
STATUS:
Waiting for enhancement request to be applied to a future version of Toad for Oracle.
