InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 09:21:10 GMT20http://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspx[quote][b]Eugene Elutin (11/13/2012)[/b][hr][quote][b]edward_hall76 (11/13/2012)[/b][hr]ok. where I work not all people know how to write tsql code and if they mess up the tsql they do not know how to fix it is why using theymuse the proc GUI. I just though there might be away of getting the GUI to reopen after running it without having to right click on the proc[/quote]That is extremely bad idea to give "people who doesn't know how to write t-sql code" access to SSMS. Are you going to install it on every user workstation? You should create some UI application which will execute stored proc. Users, don't even need to know how to do it via SSMS...[/quote]:w00t: The above is the correct answer! I can't imagine giving end-users access to SSMS...I don't even like giving SSMS access to some of my developers! Wed, 14 Nov 2012 11:57:23 GMTSteven Willishttp://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxok will have to refresh my self on php.Tue, 13 Nov 2012 09:47:30 GMTedward_hall76http://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspx[quote][b]edward_hall76 (11/13/2012)[/b][hr]ok. where I work not all people know how to write tsql code and if they mess up the tsql they do not know how to fix it is why using theymuse the proc GUI. I just though there might be away of getting the GUI to reopen after running it without having to right click on the proc[/quote]for end users, you create an application, or a web page, or some custom front end that runs the procedure on their behalf.the GUI needs to provide them with the limited input that is appropriate for their needs...drop down menus for values, for example.that application needs to validate data entered, and be ready to report results as well as report any errors that occurred to the end user.there's always work involved when releasing a functionality to end users.Tue, 13 Nov 2012 09:33:20 GMTLowellhttp://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxIs the code not in the window about the results? eg, I just right clicked and ran this sp. Above the results window I can seeUSE [Reporting1213]GODECLARE @return_value intEXEC @return_value = [dbo].[Finance_AvB_Accom_Summary] @tomonth = N'October'SELECT 'Return Value' = @return_valueGOIf I want September, I change October to September. Is this the kind of thing you are looking for?BexTue, 13 Nov 2012 09:25:13 GMTBexhttp://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspx[quote][b]edward_hall76 (11/13/2012)[/b][hr]ok. where I work not all people know how to write tsql code and if they mess up the tsql they do not know how to fix it is why using theymuse the proc GUI. I just though there might be away of getting the GUI to reopen after running it without having to right click on the proc[/quote]That is extremely bad idea to give "people who doesn't know how to write t-sql code" access to SSMS. Are you going to install it on every user workstation? You should create some UI application which will execute stored proc. Users, don't even need to know how to do it via SSMS...Tue, 13 Nov 2012 09:22:38 GMTEugene Elutinhttp://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxok. where I work not all people know how to write tsql code and if they mess up the tsql they do not know how to fix it is why using theymuse the proc GUI. I just though there might be away of getting the GUI to reopen after running it without having to right click on the procTue, 13 Nov 2012 09:15:07 GMTedward_hall76http://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxthe issue here is GUI dependancy; you've got to get used to using the TSQL window for your commands, instead of using the GUI tools.if you right click on a procedure, you get a form where you can enter the values for the parameters for the given procedure;it's much easier to simply use TSQL to do that instead.here's an example, showing both methods at the same time.note that after you populate the values for the parameters, if you click the "Script" icon in the upper left of the window, you can get a TSQL window built for you automatically.[img]http://www.stormrage.com/SQLStuff/ssms_gui_proc_params.png[/img]Tue, 13 Nov 2012 09:03:44 GMTLowellhttp://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxThe only way to bring the Execute Procedure screen back up is to right click the procedure and select the execute option.Or as I have said above, you know what information you want to pass in via the parameters so just build an EXEC string up passing in the values you wantEXEC [IT].[Insert WorkRequest proc] @DeptID = '', @ITDeptID = '', @Department = '', @problem = '', @completed = '', @notes = ''Tue, 13 Nov 2012 08:37:26 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxI have a proc called IT.InsertWorkRequestProc I right click on it and tell it to execute and it brings up a execute proc window for me to enter the information and I hit ok and it execute it. Is there some way to put an exec statement in there that will reopen the execute proc after it has ran so you can just enter the information again with out having to right click on the proc and telling it to execute.Tue, 13 Nov 2012 08:32:38 GMTedward_hall76http://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxCould you explain your need in more detail please? 'reopen'???Tue, 13 Nov 2012 08:26:51 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxsorry for not explaining very well. I have a proc[img]c:\Users|Eddie|Desktop\proc[/img] when I right click on it it brings up a execute proc I enter the information in it and hit ok it excutes. I want it to open the execute proc window again after I hit ok. is there some way to do this.Tue, 13 Nov 2012 08:26:09 GMTedward_hall76http://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxIf you know what data you want to insert via the proc, just call the proc using the exec / execute clauseEXEC [IT].[Insert WorkRequest proc] @.... = '' , @.... = '' ............Tue, 13 Nov 2012 08:17:17 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxIs there away after it has ran get it to reopen so you can insert the information using the proc without having to right click on it and telling it to execute.Tue, 13 Nov 2012 08:14:14 GMTedward_hall76http://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspx[quote][b]edward_hall76 (11/13/2012)[/b][hr]I have a stored procedure and want to know after I run it is there away to get it to reopen with out having to right click on it and telling it to execute it....[/quote]?????What do you mean by "get it to reopen"? Do you want to see its code? Right click on it and select Modify...OR:sp_helptext [stored proc name]Tue, 13 Nov 2012 08:08:30 GMTEugene Elutinhttp://www.sqlservercentral.com/Forums/Topic1384115-391-1.aspxI have a stored procedure and want to know after I run it is there away to get it to reopen with out having to right click on it and telling it to execute it.USE [IT]GO/****** Object: StoredProcedure [IT].[Insert WorkRequest proc] Script Date: 11/13/2012 08:45:29 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGO-- =============================================-- Author: <Author,,Name>-- Create date: <Create Date,,>-- Description: <Description,,>-- =============================================ALTER PROCEDURE [IT].[Insert WorkRequest proc] -- Add the parameters for the stored procedure here@DeptID int,@ITDeptID int, @Department nvarchar(25), @problem nvarchar(50), @completed nchar(4),@notes nvarchar(255)--@StartDate [datetime],--@EndDate [datetime]ASBEGIN -- SET NOCOUNT ON added to prevent extra result sets from -- interfering with SELECT statements. SET NOCOUNT ON;insert into IT.WorkRequest (DeptID, ITDeptID, Department, problem, completed, notes) Values ( @DeptID, @ITDeptID, @Department, @problem, @completed, @notes )----select * from it.WorkRequestendTue, 13 Nov 2012 08:01:39 GMTedward_hall76