DOC: T-SQL Debugger Server Setup Provides Incorrect Location

 Last reviewed: April 7, 1997
Article ID: Q166280
The information in this article applies to:
  • Microsoft Visual Basic Enterprise Edition for Windows, version 5.0

SUMMARY

The documentation for setting up Server-Side T-SQL Debugging incorrectly states that Sdi_nt4.exe and Readme.txt can be found in the \CliSrv\Tsql\SrvSetup directory of your Visual Basic 5.0 Enterprise installation.

The documentation should read that Sdi_nt4.exe and Readme.txt can be found in the \Tools\Tsql\Srvsetup directory of your Visual Basic 5.0 Enterprise CD-ROM.

MORE INFORMATION

The following is the corrected version of the documentation:

Server-Side Setup With SQL Server version 6.5 and Service Pack 1 installed, you can install and register the SQL Debugger interface and Remote Automation component on the server. These components are located in the \Tools\Tsql\Srvsetup directory of your Visual Basic 5.0 Enterprise CD-ROM. On Windows NT 4.0, simply run the setup program Sdi_nt4.exe.

Note: For setup on NT Server 3.51, you must manually copy and register the necessary files. Complete instructions for this process are included in the Readme.txt file in the \Tools\Tsql\Srvsetup directory of your Visual Basic 5.0 Enterprise CD-ROM.

REFERENCES

(c) Microsoft Corporation 1997, All Rights Reserved. Contributions by Jon Fowler, Microsoft Corporation

Keywords : vb5all kbdocerr
Version : 5.0
Platform : WINDOWS
Issue type : kbdocerr

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.

Last reviewed: April 7, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.