ACC2000: Debugging and Troubleshooting Tips for Linked SQL Tables

Article translations Article translations
Article ID: 209489 - View products that this article applies to.
This article was previously published under Q209489
This article has been archived. It is offered "as is" and will no longer be updated.
Moderate: Requires basic macro, coding, and interoperability skills.

Expand all | Collapse all


This article lists some techniques that you can use to determine indirect causes of error messages when using linked (attached) SQL tables:
  1. Make sure the connection information, such as server name, login ID, and password, is correct. If any of this information has changed, you may have to delete and then re-create the links with the new connection information.
  2. 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.
  3. Use another application, such as one of the following, on the same computer and try to link the same data source:

    • SQL Server Enterprise Manager
    • PowerBuilder
    • MSQuery
  4. 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.
  5. 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.
  6. 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.
  7. Try increasing the ODBCTimeout setting on the property sheet of the query.
  8. Rename the current Odbc32.dll, Dbnmpntw.dll, and Sqlsrv32.dll files, restart the server, and reinstall ODBC.


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.


Article ID: 209489 - Last Review: October 11, 2013 - Revision: 2.1
  • Microsoft Access 2000 Standard Edition
kbnosurvey kbarchive kbhowto kbinterop kbusage KB209489

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from