Single-stepping through a SQL Server stored procedure does not display error messages at the point where the errors occur in Visual C++

Article translations Article translations
Article ID: 155716 - View products that this article applies to.
This article was previously published under Q155716
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

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

STATUS

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

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.

Properties

Article ID: 155716 - Last Review: February 28, 2014 - Revision: 4.0
APPLIES TO
  • Microsoft Visual C++ 2005 Express Edition
  • Microsoft Visual C++ .NET 2003 Standard Edition
  • Microsoft Visual C++ .NET 2002 Standard Edition
  • Microsoft Visual C++ 4.2 Enterprise Edition
  • Microsoft Visual C++ 5.0 Enterprise Edition
  • Microsoft Visual C++ 6.0 Enterprise Edition
Keywords: 
kbnosurvey kbarchive kbtshoot kbbug kbsqlprog kbdatabase kbeedition kbdebug kbprb KB155716

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com