ACC: How to Determine Version of INSTCAT.SQL File on Server

 Last reviewed: May 20, 1997
Article ID: Q100467
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1, 2.0, 7.0, 97

SUMMARY

Advanced: Requires expert coding, interoperability, and multiuser skills.

Using the SQL Server ODBC driver with Microsoft Access requires that you run the INSTCAT.SQL file on the ODBC installation disks. This article describes the SQL stored procedure that you can use to query for the version number of the INSTCAT.SQL file that was run against the SQL Server computer.

MORE INFORMATION

The following syntax can be executed in a pass-through query in Microsoft Access 2.0, 7.0 and 97 as well as in the Query window of SQL Server Administration Facility (SAF) for MS-DOS, OS/2, Microsoft Windows or any other operating system in which you can execute a stored procedure: 

   sp_server_info 500
The attribute_value field of the returned row contains the version number. If an empty recordset is returned, it is likely that the INSTCAT.SQL file was not run on the server. The result will resemble the following: 

   attribute_id   attribute_name      attribute_value
   --------------------------------------------------
   500            SYS_SPROC_VERSION   01.00.2101
OS/2 is manufactured by International Business Machines Corporation, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Keywords : kb3rdparty OdbcOthr
Version : 1.0 1.1 2.0 7.0 97
Platform : WINDOWS
Hardware : X86
Issue type : kbhowto

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: May 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.