It should not unless you have already fired off the command in SQL Server. If
so, stopping debugging only stops the client, as it does not contact the
server, at all. At this point, the code is still running (on the server)
despite you stopping it (on the client). You have to break before you contact
the server to stop server code.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************** ************
Think Outside the Box!
*************** ************
"ENathan" wrote:
I have a public sub in a class that does something like:
If ValuesChanged() Then
UpdateDatabase
End If
ValuesChanged and UpdateDatabase are Private functions within the class.
My problem is, when I finish debugging ValuesChanged and click the stop
debugging button, it appears the code continues behind these scenes and runs
UpdateDatabase.
Why doesn't it stop or how can I get it to stop? TIAFYT