Knowledge Base

FIX: Cannot Open Stored Procedure from Call Stack Context

Article ID: 159576

Article Last Modified on 10/15/2002

Microsoft Visual C++ 4.2 Enterprise Edition

This article was previously published under Q159576

SYMPTOMS

When you debug a stored procedure and you close the associated source code window, you cannot reopen it from the call stack context.

MORE INFORMATION

Steps to Reproduce the Problem

Open a SQL Server stored procedure and start debugging it.
When the debugger stops at the first executable statement, close the Source Code window for the procedure.
Go to the call stack and double-click the procedure name to bring up the source code window.

A 'Find Source' dialog box might appear and request the stored procedure's path. When you cancel this dialog box, the debugger opens a disassembly window at an arbitrary address.

RESOLUTION

Select the View/Project Workspace menu to open the Project Workspace window. Open the stored procedure from the data pane in the Project Workspace window. If you double-click the procedure name in the call stack, the debugger points (with a green arrow) to the correct statement in the procedure where the debugger is stopped. Now you can continue debugging.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual C++ version 5.0.

Additional query words: kbVC420bug kbDSupport

Keywords: kbbug kbfix kbsqlprog kbeedition kbvc500fix kbdebug KB159576