|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 10:39 AM
Points: 2,556,
Visits: 4,398
|
|
edward_hall76 (11/13/2012) 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
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...
_____________________________________________ "The only true wisdom is in knowing you know nothing" "O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!" (So many miracle inventions provided by MS to us...)
How to post your question to get the best and quick help
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: 2 days ago @ 7:57 AM
Points: 1,111,
Visits: 1,394
|
|
Is the code not in the window about the results?
eg, I just right clicked and ran this sp. Above the results window I can see USE [Reporting1213] GO
DECLARE @return_value int
EXEC @return_value = [dbo].[Finance_AvB_Accom_Summary] @tomonth = N'October'
SELECT 'Return Value' = @return_value
GO
If I want September, I change October to September. Is this the kind of thing you are looking for?
Bex
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Today @ 4:31 AM
Points: 11,648,
Visits: 27,762
|
|
edward_hall76 (11/13/2012) 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
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.
Lowell
--There is no spoon, and there's no default ORDER BY in sql server either. Actually, Common Sense is so rare, it should be considered a Superpower. --my son
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Friday, May 10, 2013 2:46 PM
Points: 53,
Visits: 190
|
|
| ok will have to refresh my self on php.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Yesterday @ 10:03 PM
Points: 284,
Visits: 1,248
|
|
Eugene Elutin (11/13/2012)
edward_hall76 (11/13/2012) 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 procThat 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...
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!
|
|
|
|