User working in Editor window on a SQL Server script. He presses F5 or F9 to run the script. The focus changes from the Editor script window to the result window. This is annoying because most of the time a developer is just running the script to check if it's running correctly and will want to stay in the script window to continue coding.
Example steps to reproduce:
1. Open an Editor window. Run a select statement on a table that doesn't exist such as "select * from table_10" press either F5 or F9 to run it.
2. The Editor will focus on the result window error table not found. You have to click on the script window to continue typing.
3. Fix the error by selecting from a table which exist, such as "select * from table_1" press either F5 or F9 to run it.
4. The Editor will focus on the result set instead of staying in the script window. You have to click on the script pane to continue typing.
5. Run the correct script again using F5 or F9. This time the focus stays in the script pane.
