INFO: Known Issues with the Visual Basic T-SQL Debugger and SQL Server 2000 (310650)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q310650 SUMMARY
Since the release of SQL Server 2000, Microsoft has identified a number of issues between SQL Server 2000 and the Visual Basic 6.0 T-SQL Stored Procedure Debugger add-in, which originally released in 1998. This article lists the most significant issues.
REFERENCESFor additional information about the T-SQL Debugger add-in and other known issues, click the article numbers below
to view the articles in the Microsoft Knowledge Base:
166280 DOC: T-SQL Debugger Server Setup Provides Incorrect Location
170496 INF: Tips for Debugging Stored Procedures from Visual Basic
172099 PRB: T-SQL - Running Remote and Local SQL Debugging
175868 BUG: T-SQL Debugger Does Not Run on NT with User Account
179023 FIX: T-SQL Debugger Hangs When User Has No Execute Permission
190211 PRB: Problems When Visual Basic 5.0 and 6.0 Are Installed on the Same System
190212 BUG: Add-Ins Only Visible to the User Who Installs VB
190451 BUG: Exiting VB While T-SQL Debugger Is Running Causes Hang
191513 BUG: T-SQL Debugger Is Not Invoked Calling Second Stored Procedure
200888 PRB: Cannot Invoke T-SQL Debugger to Automatically Appear Using ADO
223060 FIX: T-SQL Shows Incorrect Parameters in Local Variables Window
254464 PRB: Can't Add the T-SQL Debugger to the Visual Basic Add-in Manager
281297 FIX: Visual Studio 6.0 T-SQL Debugger Buffer Overflow
Modification Type: | Major | Last Reviewed: | 9/29/2006 |
---|
Keywords: | kbDatabase kbinfo kbTSQL KB310650 |
---|
|