Msgbox from Stored Procedure

Hi,
Can I Call MsgBox Function From SP ?No. Transact SQL doesn't have any UI functionality. For that you need to use
a host language such as VB or C# for example.
David Portas
SQL Server MVP
--|||As long as Procedures are executed on the server that would make no sense to
display a Msgbox. If ou want to debug your sp, fill in some PRINT commands
to get some information.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"DMP" <debdulal.mahapatra@.fi-tek.co.in> schrieb im Newsbeitrag
news:OVQx1XXRFHA.2604@.TK2MSFTNGP10.phx.gbl...
> Hi,
> Can I Call MsgBox Function From SP ?
>|||Hi,
What are you trying to achieve, are you trying to debug something or
are you trying to display something to the end user.
If you are trying to debug something in a stored procedure then I
personally use a debug table posting results to the table as I go
through the stored procedure. This only any good for debuging.
If you are trying to display something to the end user then use an
OUTPUT parameter in the stored procedure and get the value on the
end-users computer and display that throught the msgbox interface.
Regards
Alex|||Thanks to everybody,
Basically I have three sp let sp1,sp2,sp3
From VB I call sp1,
sp1 call to sp2 and dpending the return value of sp2 , End user will take
dicission that
sp3 will be called or not like VB msgbox("do you want to continue ?",
vbYesNo),
If vbYes then calls to sp3 else return from sp2,sp1
This is my goal...
"Alex" <alex@.intralan.co.uk> wrote in message
news:1113985604.270498.57780@.l41g2000cwc.googlegroups.com...
> Hi,
> What are you trying to achieve, are you trying to debug something or
> are you trying to display something to the end user.
> If you are trying to debug something in a stored procedure then I
> personally use a debug table posting results to the table as I go
> through the stored procedure. This only any good for debuging.
> If you are trying to display something to the end user then use an
> OUTPUT parameter in the stored procedure and get the value on the
> end-users computer and display that throught the msgbox interface.
> Regards
> Alex
>|||you either need to design out the decision or:
All in VB:
Call SP1
Processes results
Ask User Continue?
Yes? Call SP3
SP's run not just "on" the server, but "in" the server - the only ways that
an SP can communicate is via return codes, output parameters, result sets,
print statements (rare IMHO), exceptions (raiserror), or indirectly via COM
objects - see sp_oa* sp's. (there are more methods, but I think you get the
point). IE the pre-existing communications channels via the comms protocol
in use which is normally TDS (tabular data stream) over TCP/IP.
Whats more, if you call a COM interface it really should be prompt -
stalling SQL Server for some external process of indefinite length falls
into the really really really bad technique category.
"DMP" <debdulal.mahapatra@.fi-tek.co.in> wrote in message
news:uKw%23dWYRFHA.244@.TK2MSFTNGP12.phx.gbl...
> Thanks to everybody,
> Basically I have three sp let sp1,sp2,sp3
> From VB I call sp1,
> sp1 call to sp2 and dpending the return value of sp2 , End user will take
> dicission that
> sp3 will be called or not like VB msgbox("do you want to continue ?",
> vbYesNo),
> If vbYes then calls to sp3 else return from sp2,sp1
> This is my goal...
> "Alex" <alex@.intralan.co.uk> wrote in message
> news:1113985604.270498.57780@.l41g2000cwc.googlegroups.com...
>sql