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

ID: Q200888

The information in this article applies to:

ActiveX Data Objects (ADO), versions 2.0, 2.01, 2.1
Microsoft Visual Basic Enterprise Edition for Windows, versions 5.0, 6.0

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.

CAUSE

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

RESOLUTION

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

STATUS

This behavior is by design.

Additional query words:


Keywords          : kbADO kbADO200 kbADO201 kbADO210 kbDatabase kbTSQL kbVBp kbVBp500 kbVBp600 kbGrpVBDB 
Version           : WINDOWS:2.0,2.01,2.1,5.0,6.0
Platform          : WINDOWS 
Issue type        : kbprb

Last Reviewed: April 3, 1999