DOCUMENT:Q223060 11-JAN-2001 [vbwin] TITLE :FIX: T-SQL Shows Incorrect Parameters in Local Variables Window PRODUCT :Microsoft Visual Basic for Windows PROD/VER:WINDOWS:6.0 OPER/SYS: KEYWORDS:kbservicepack kbSQLServ kbTSQL kbVBp600bug kbVS600sp2 kbVS600SP1 kbVS600sp3fix kbGrpDSV ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Professional Edition for Windows, version 6.0 - Microsoft Visual Basic Enterprise Edition for Windows, version 6.0 ------------------------------------------------------------------------------- SYMPTOMS ======== When using the Visual Basic T-SQL Debugger to debug SQL Server 7.0 stored procedures, you might see incorrect values for input parameters in the Local Variables window. RESOLUTION ========== To resolve this problem, install Visual Studio 6.0 Service Pack 3 on the client (Visual Basic) computer. You do not need to install the updated T-SQL Debugger components on the server (SQL Server) computer. STATUS ====== Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual Studio 6.0 Service Pack 3. For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base: Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why Q194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed MORE INFORMATION ================ Steps to Reproduce Behavior --------------------------- 1. Open a new Visual Basic Standard Exe project. Form1 is created by default. 2. Open the Data View window. 3. Create a Data Link to a SQL Server 7.0 Pubs database. 4. Open the Stored Procedures folder. 5. Right-click the reptq3 stored procedure and select Debug. 6. Populate the three parameters. 7. Step into the stored procedure. You'll see that all three parameters in the Local Variables window have the same value. This problem only occurs with SQL Server 7.0. Additional query words: ====================================================================== Keywords : kbservicepack kbSQLServ kbTSQL kbVBp600bug kbVS600sp2 kbVS600SP1 kbVS600sp3fix kbGrpDSVBDB Technology : kbVBSearch kbAudDeveloper kbZNotKeyword6 kbZNotKeyword2 kbVB600Search kbVBA600 kbVB600 Version : WINDOWS:6.0 Issue type : kbbug Solution Type : kbfix ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 2001.