PRB: Cannot Invoke T-SQL Debugger to Automatically Appear Using ADO

View products that this article applies to.

This article was previously published under Q200888

Expand all | Collapse all

SYMPTOMS

When using Visual Basic 5.0 and stepping through ADO code that executes a SQL Server stored procedure, the T-SQL Debugger does not automatically start. However, using similar RDO code does start the T-SQL Debugger.

Back to the top

CAUSE

Visual Basic 5.0 does not have the appropriate hooks in place to automatically invoke the T-SQL Debugger when using ADO.

Back to the top

RESOLUTION

Upgrade to Visual Basic 6.0 and ADO 2.0 or later because these products have the appropriate hooks in place to automatically invoke the T-SQL Debugger.

Back to the top