ACC2000: Debugging and Troubleshooting Tips for Linked SQL Tables

ID: Q209489


The information in this article applies to:
  • Microsoft Access 2000

Moderate: Requires basic macro, coding, and interoperability skills.


SUMMARY

This article lists some techniques that you can use to determine indirect causes of error messages when using linked (attached) SQL tables:

  • Check for multiple, corrupted, or outdated copies of the following files.

    In Microsoft Windows 95 or later, use Windows Explorer to search for copies of the following files:
    
       ODBC32.DLL   - dated  01-22-1999 or later, with 198000 bytes
       DBNMPNTW.DLL - dated  11-20-1998 or later, with 33040 bytes
       SQLSRV32.DLL - dated  11-20-1998 or later, with 508176 bytes
       NETAPI32.DLL and NETAPI - depends on the network being used
    
       NOTE: The sizes and dates referenced are correct if the
       files were installed by Microsoft Access 2000. 
    Make sure that all these files are in their appropriate locations. All of the files are usually installed in the \Windows\System folder.

  • Use another application, such as one of the following, on the same computer and try to link the same data source:

    • SQL Server Administration Facility (SAF)
    • PowerBuilder
    • MSQuery

  • If you cannot access the data source from another application, you may have a problem with the network, and not with Microsoft Access or the Microsoft Open Database Connectivity (ODBC) driver.
  • Try to link another data source, such as another SQL Server table, from a different database server. If you can link the other data source, the original server may be unavailable, or you may need to reconfigure the entry for that server by using the ODBC Administration utility.
  • Try to link the same data source from a different computer. If you still cannot gain access to the SQL Server computer, you may have a network-wide problem, or perhaps the server is down or is not communicating.
  • Try increasing the ODBCTimeout setting on the property sheet of the query.
  • Rename the current Odbc32.dll, Dbnmpntw.dll, and Sqlsrv32.dll files, restart the server, and reinstall ODBC.


REFERENCES

PowerBuilder is manufactured by Powersoft Corporation, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional query words:

Keywords : kbinterop kbusage kbdta OdbcOthr
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbhowto


Last Reviewed: September 20, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.