Is there a way within asp.net to verify that a stored procedure has completed running before executing the next line of code?

Thanks for the help!

Are you having trouble with this? The call to the stored proc should be blocking until it is complete.

Woody Z
http://www.learntoprogramnow.com

I guess I am having a problem with this because it seems like the next few lines of code beneath the execution of the stored proc are being ran before the stored proc is finished.

During the execution of the stored procedure, does asp.net wait until it has confirmation that the process has finished before it executes the next line? If it does, is there a way to make the program wait 2-3 seconds before executing the next line which requeries the table just effected by the stored procedure?

Thanks

I assume you are using a command object, and when you call the ExecuteNonQuery method this will block until it returns from the stored proc. It isn't so much waiting for "confirmation", it is just a typical method call that must run through its internal code before it can return.

What is youir actual problem? I think you are asking for solution, but you aren't describing the problem.

Woody Z
http://www.learntoprogramnow.com

We have a multiple step application that displays a record count and a "Total Pounds" in a text box. This gives the user the ability to check and make sure that the information was collected from multiple source is correct. The user then starts the stored procedure which takes all that information and places it in the appropriate table throughout our Sql Server. After that, it requeries the records and if they have all been moved around successfully, there should be no data in the original table and thus reports a 0 - Record Count and 0 - Pounds. Every now and then, when the requery takes place, it reports a few records and pounds are still in there. When you force a requery, all of the records and pounds have been moved and it zeros out. I hope that is not too conviluted!!! Thanks for your help!

Unless you are executing the stored proc call in a separate thread, the call should be blocking. There might be something else going on that isn't clear at this time that we need to consider.

Woody Z
http://www.learntoprogramnow.com