Suggestion to redesign the visual stored procedure editor of dbForge.

Uh... there are a number of major misses here in 4.0.

I login to a database, expand the Programmability section, then right-click a procedure and select 'Edit Procedure.' The script that is generated is a CREATE PROCEDURE method, which out of the box won't work because the procedure already exists.

Okay, so I change it to ALTER PROCEDURE and press F5 to rebuild the procedure. I get a dialog box prompting me for parameters! Oh, I guess F5 means RUN the procedure? No, that's not what I want. It looks to me like there's some other command for 'run script' ... but I look and look and can't find it. I can't find a 'Run' button at all, or an 'Execute' button.

Oh, wait, the SQL Toolbar is hidden by default. I show that, click the 'Execute' button - and get the dialog again!

Why can't I just execute the script? Why is it forcing me to execute the procedure? Maddening.

Worse -- I try to save my script and the program says 'Object has invalid source text and cannot be saved.' WHAT??? What if I am working on something and want to save it, even if it won't compile at the moment?

I don't mean to sound snarky, but these problems make the program unusable, sorry! Back to SSMS for me.