PRB: SQL Single-Stepping Does Not Display Errors as They Occur

Last reviewed: June 26, 1997
Article ID: Q155716

The information in this article applies to:

Microsoft Visual C++, Enterprise Edition, versions 4.2, 5.0

SYMPTOMS

When single-stepping through a SQL Server stored procedure, error messages, if generated, are not displayed at the point where the error occurred.

MORE INFORMATION

To reproduce this behavior, create and single-step through the following stored procedure in the SQL Server Pubs sample database:

CREATE PROCEDURE sp_trigger AS

INSERT authors

    VALUES ('123-21-2321', 'Redmond', 'Ricky', '206/555-1212',
          '123 Nowhere St.', 'Redmond', 'WA', '98989', DEFAULT )

DECLARE @a INTEGER SELECT @a = 4/2 RETURN

The INSERT statement fails because there is no DEFAULT defined for the last field. However, the user is not notified that the insertion failed until the stored procedure completes.

STATUS

We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords : kbprg vcbuglist420 vcbuglist500 VCEntIss VCEntSQLDebug
Technology : kbMfc
Version : 4.2 5.0
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.