Studio - Execute looses cursor location

Discussion of open issues, suggestions and bugs regarding database management and development tools for SQL Server
Post Reply
slavanaway
Posts: 2
Joined: Tue 25 Nov 2014 17:51

Studio - Execute looses cursor location

Post by slavanaway » Tue 25 Nov 2014 18:07

When a SQL is run, using F5 or F8, my cursor always goes to the first line of the SQL window.

I have SQL tabs with multiple SQL statements. I run a SQL that is not the first one. When I run the SQL using F8 or highlight the text and run using Execute on the toolbar or F5, the cursor moves to line 1 character 1.

Is this what others are seeing? Is there a setup I missed?

Thanks

Sam

alexa

Re: Studio - Execute looses cursor location

Post by alexa » Wed 26 Nov 2014 16:52

Could you please provide us a screenshot of dbForge taken at that time and specify the version of dbForge and SQL Server?

You can send a reply straight to our support system at supportATdevartDOTcom

slavanaway
Posts: 2
Joined: Tue 25 Nov 2014 17:51

Re: Studio - Execute looses cursor location

Post by slavanaway » Mon 15 Dec 2014 17:39

I posted via a reply from my email. I don't see the update yet.
I use this construct to make more adaptable sqls when researching issues;

select *
from table1
where (colA like @v1 or @v1 is null);

This opens a parameter window (a lot like the :v1 bind variable in Toad) and allows edits to the @ variables.

When I have many scripts in a single sql tab, the cursor goes to row 1 column 1 when I execute the query with the @ variables in the where clause.

This brings up another point with the @ variables and the popup.

If I have a tab open and write a script with an @ variable. I run the sql with the @ vaiable and I get the popup. If I run a sql that does not have the @ variable of delete all the code in the tab (ctrl-a / delete) I still get the popup. The popup should only be active on the sql stmt that has the @ variable(s).

alexa

Re: Studio - Execute looses cursor location

Post by alexa » Wed 17 Dec 2014 10:42

Could you please resend a screenshot of dbForge taken at the time when the problem happens and specify the version of dbForge and SQL Server?

Please try sending a reply to alexaATdevartDOTcom

Post Reply