Transactions executed in scripts do not apply in schema selected from Current Schema drop down me (4245502)

Transactions executed in scripts do not apply in schema selected from Current Schema drop down menu of Editor's toolbar, in case this schema is different than the one that is logged on to. All transactions are applied to the logged schema.

Executing any transaction with Execute as Statement (F9) option will be applied to the schema that is selected under the Current Schema drop down, in case this schema is different than the schema that is logged on to. Toad issues an "ALTER SESSION SET" statement before and after the execution of the command to change schema.

Executing transaction(s) with Execute as Script (F5) option will be applied to the logged on schema, regardless of the selected schema from Current Schema drop down. Toad does not issue "ALTER SESSION SET" statements. Therefore, the schema name is required to be appended to the object names if transactions need to be applied to a different schema other than the one that is logged on to.

RESOLUTION #1:
Execute the query as a statement (F9), instead of as a script (F5).

RESOLUTION #2:
Make sure that the user is not logged in as sysdba.   User should be logged in as normal for the Current Schema option to take effect.