The user opens a procedure and steps into the procedure. Then the user goes to the Schema browser and edits a table. Upon issuing a commit, Toad will hang and never come back.
WORKAROUND
Option 1: Go to view >> Options >> General >> Check "Allow Multiple copies of Toad to be Loaded"
Then open a different copy of Toad if you are planning to edit data and debug a procedure at the same time.
Option 2: Halt the debugger before editing data in your Oracle database.
STATUS
This issue is fixed in Toad 8.0. This version can be downloaded at http://questsupportlink.quest.com/prod_upgrade_alert.asp.
