PRB: "Set Next Statement" Does Not Work During SQL Debugging

Last reviewed: January 22, 1998
Article ID: Q179757

The information in this article applies to:

Microsoft Visual C++, 32-bit Enterprise Edition, version 4.2

SYMPTOMS

When debugging a Microsoft SQL Server stored procedure using MSDEV IDE, the “Set Next Statement” option does not work correctly.

RESOLUTION

This is by design. "Set Next Statement" is not supported for SQL debugging.

MORE INFORMATION

When the debugger stops at a statement in the stored procedure, if you move the insertion point to a new statement and click the “Set Next Statement” option, the debugger does not move to the new statement.

During SQL debugging, SQL server indicates what the next statement will be. The debugger doesn't have the same information that it receives from native debug information (.pdb, and so on) during C++ debugging. Skipping SQL statements may cause unpredictable results so this option is not implemented.

Additional query words: SQLDebug
Keywords : VCEntIss
Version : WINDOWS:4.2
Platform : 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: January 22, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.