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



The information in this article applies to:

  • ActiveX Data Objects (ADO) 2.0
  • ActiveX Data Objects (ADO) 2.01
  • ActiveX Data Objects (ADO) 2.1 SP2
  • ActiveX Data Objects (ADO) 2.5
  • ActiveX Data Objects (ADO) 2.6
  • Microsoft Visual Basic Enterprise Edition for Windows 5.0
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0

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.

Modification Type:MajorLast Reviewed:8/23/2001
Keywords:kbDatabase kbDSupport kbMDACNoSweep kbprb kbTSQL KB200888