Article ID: 190451 - Last Review: May 13, 2003 - Revision: 3.0

BUG: Exiting VB While T-SQL Debugger Is Running Causes Hang

This article was previously published under Q190451

On This Page

Expand all | Collapse all

SYMPTOMS

Closing down Visual Basic while the T-SQL debugger is running hangs them both.

RESOLUTION

Before closing down Visual Basic, make sure T-SQL Debugging is not running.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Open a New Standard EXE project. Form1 is created by default.
  2. Launch Add-In Manager under menu Add-Ins. Make sure Visual Basic T-SQL Debugger is checked.
  3. From the Add-Ins menu, select T-SQL Debugger. This will bring up a dialog box titled "Visual Basic Batch T-SQL Debugger."
  4. On the Settings tab, fill in the appropriate information to establish a connection.
  5. On the Stored Procedure tab, choose a stored procedure from the drop-down combobox. Fill in the value of parameters, if applicable.
  6. Click Execute to start running the debugging.
  7. When the T-SQL debugger loads, press the F8 key (or click the Step Into button) to step into the code.
  8. Close down Visual Basic by clicking Exit under the File menu.

APPLIES TO
  • Microsoft Visual Basic 6.0 Learning Edition
  • Microsoft Visual Basic 6.0 Professional Edition
  • Microsoft Visual Basic 6.0 Enterprise Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition
Keywords: 
kbbug KB190451
 

Article Translations