Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SJBUSHELL
Starting Member
2 Posts |
Posted - 2002-07-25 : 06:35:07
|
| Hi.I have been given a task to develop some stored proceedures to be called from VB. I haven't actually had any formal training but have managed to write a dynamic stored proceedure which is executed by sp_executeSQL. The question I have is is there anyway I can get a 'progress' of how the execution is going so I can update a progress bar in VB or do i have to wait until sp_executeSQL has finished executing my SQL and just put out a 'Retrieving Data, Please Wait' message in VB?.Just when you think things can't get any worse, they do. |
|
|
VyasKN
SQL Server MVP & SQLTeam MVY
313 Posts |
Posted - 2002-07-25 : 07:34:09
|
| You could try the Microsoft style progress bar :-) Just before you call the procedure, set the progress bar to 99% and wait till the stored procedure completes. When it does, set the progress bar to 100% ;-)Seriously, if your stored procedure is performing multiple taks, then you could use a RAISERROR (WITH NOWAIT option) command in between those tasks to return progress info to the client application. I haven't tried this myself though.--HTH,Vyashttp://vyaskn.tripod.comEdited by - vyaskn on 07/25/2002 07:34:44 |
 |
|
|
SJBUSHELL
Starting Member
2 Posts |
Posted - 2002-07-25 : 07:48:44
|
| Thanks VyasK. Unfortunately the sql is just one call, I have used dynamic sql as the VB program can have many parameters but basicaly it is just issuing one Select statement. It may be that I'm not going the right way about the whole thing. Still if the users have to wait then it gives them time to see what a marvelous program I've written!Just when you think things can't get any worse, they do. |
 |
|
|
|
|
|