PRB: Cannot Invoke T-SQL Debugger to Automatically Appear Using ADO
Article ID: 200888
Article Last Modified on 8/23/2001
APPLIES TO
- Microsoft ActiveX Data Objects 2.0
- Microsoft ActiveX Data Objects 2.01
- Microsoft ActiveX Data Objects 2.1 Service Pack 2
- Microsoft ActiveX Data Objects 2.5
- Microsoft ActiveX Data Objects 2.6
- Microsoft Visual Basic 5.0 Enterprise Edition
- Microsoft Visual Basic 6.0 Enterprise Edition
This article was previously published under Q200888
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 or later because these products have the appropriate hooks in place to automatically invoke the T-SQL Debugger.
STATUS
This behavior is by design.
Keywords: kbtsql kbdatabase kbprb kbmdacnosweep KB200888