executing SQL not in different databases

[jkuiper]

I have several database connections in my database explorer. If I create a new SQL and execute it in the bolmate database on router9, everything works fine. Then I close the bolmate database on router9 and goes to the bolmate database on my localhost. If I execute the same script, without closing it, it opens bolmate database on router9 again and gives the result of the wrong database. (see my log)

SQL1.sql: Query opened in 0,936s [0,928s exec, 0,008s fetch]
4568 records selected
SQL1.sql: Query opened in 1,014s [1,014s exec, < 0,001s fetch]
4568 records selected
SQL1.sql: Query opened in 1,013s [1,013s exec, < 0,001s fetch]
4568 records selected
Connection 'bolmate.router9' was disconnected.
Connection 'bolmate.localhost' was connected.
Connection 'bolmate.router9' was connected.
SQL1.sql: Query opened in 1,678s [1,666s exec, 0,012s fetch]
4568 records selected

Why will dbForge studio standard 3.1.222 not execute my script in a different database?

[Duke]

Once you open SQL document it appears bound to specific connection and remains so regardless whether you open another connection or not. To associate documents with another connection you need to select is from combo box on toolbar when the document is active.
For more information please refer to documentation.