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

 Last reviewed: June 26, 1997
Article ID: Q156851
The information in this article applies to:
  • Microsoft Visual C++, Enterprise Edition, version 4.2

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.

MORE INFORMATION

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 : kbprg kbtool VCEntIss VCEntSQLDebug
Technology : kbMfc
Version : 4.2
Platform : NT WINDOWS
Issue type : kbprb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 26, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.