ACC1x: Query Fails When Linked SQL Server Table Cannot Be Found

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

SYMPTOMS

When attempting to use an attached SQL Server table, you may receive the following error message:

   Couldn't execute query; couldn't find linked table.
   Invalid object name <TABLE_NAME>.

   -or-

   Unable to connect to data source.

CAUSE

The following two conditions are most likely to cause this error message:

  • There is an incorrect entry in the [SQLSERVER] section of your WIN.INI file.

    The [SQLSERVER] section of your WIN.INI file should look like the following example:

          [SQLSERVER]
          MYSERVER=dbnmp3,\\MYSERVER\PIPE\SQL\QUERY
          YOURSRVR=dbnmp3,\\YOURSRVR\PIPE\SQL\QUERY
    

    This error is caused by an incorrect server name (MYSERVER or YOURSERVR) or extra spaces in the path.

  • The SQL database server is overloaded or unavailable.

RESOLUTION

Verify that the [SQLSERVER] section of your WIN.INI file has the correct entry for the server you are attempting to attach. Then check with the system administrator to see if the SQL database server is available for transactions, operating properly, and not overloaded.


Additional query words: kbtshoot tshoot
Keywords : kberrmsg kbusage OdbcOthr
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided


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.