Microsoft KB Archive/179757

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

Article ID: 179757

Article Last Modified on 7/17/2001

-

APPLIES TO


 * Microsoft Visual C++ 4.2 Enterprise Edition

-



This article was previously published under Q179757



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: kbeedition kbprb KB179757

-

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

© Microsoft Corporation. All rights reserved.