Microsoft KB Archive/156851

= PRB: Run to Cursor and Breakpoints Don't Work After Debug.Break =

Article ID: 156851

Article Last Modified on 10/15/2002

-

APPLIES TO


 * Microsoft Visual C++ 4.2 Professional Edition

-



This article was previously published under Q156851



SYMPTOMS
"Run to cursor" and breakpoints do not work after Debug.Break when debugging a SQL Server stored procedure on Windows 95.



RESOLUTION
Debug.Break is not supported when debugging a SQL stored procedure. This is by design.

When debugging a SQL stored procedure, the debugger always stops on the first line of executable code in the stored procedure. You can then set breakpoints and use the "Run to cursor" feature.



STATUS
This behavior is by design.



Steps to Reproduce Problem

 * 1) Start debugging a SQL Server stored procedure and immediately select Break from the Debug menu.
 * 2) Right-click the stored procedure window and select the option "Run to Cursor".

The stored procedure will run to completion. It will not stop at cursor. If there are additional breakpoints, these will not be hit.

Keywords: kbbug kbsqlprog kbprogramming kbeedition kbdebug kbprb KB156851

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.