Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 200888 - Last Review: August 23, 2001 - Revision: 1.1
PRB: Cannot Invoke T-SQL Debugger to Automatically Appear Using ADO
This article was previously published under Q200888
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.
Visual Basic 5.0 does not have the appropriate hooks in place to automatically invoke the T-SQL Debugger when using ADO.
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.
This behavior is by design.
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 Enterprise Edition for Windows 6.0
| kbdatabase kbmdacnosweep kbprb kbtsql KB200888 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate