How To Fix MS Access Run-time 3146 ODBC Call Failed Error?


Does your Access database showing “3146 – ODBC Connection Failed” error?  Looking for the fixes to resolve this issue? Then just go through the complete post and get the best resolution to solve this.

The “3146 – ODBC Connection Failed” error message displays as a result of a faulty network connection. This error might occur at any point within the database when setting up and associated with the database on an additional PC. The most common alternatives are either a faulty network card or SQL will terminate the connection after 30 minutes of inactivity for security reasons.

If you’re receiving error without program and database sitting idle for more than 30 minutes, then you must contact IT professionals so as to make certain that your network connection is set up and operating properly.

This run-time error occurs at the time when the system has any issue with the software and hardware components. The main reason for this error is to take place is when a system gets corrupted in Windows OS.

This article will be guiding you to get rid of ODBC call failed error 3146 in MS Access using manual method and even a fully automated solution. Moreover, errors that take place regularly in relation to Access error 3146 ODBC call failed, will too be sent.

Fix Microsoft Access Issues
Run a database Scan with Stellar Access Database Repair Tool to repair inconsistent Access database. After the scan is complete, the repair process will restore the database to its normal state fixing all the errors.

By clicking the button above and installing Stellar Repair for Access (14.8 MB), I acknowledge that I have read and agree to the End User License Agreement and Privacy Policy of this site.

What is Run-Time Error 3146?


When Microsoft Access tries to enter the SQL Server 2000 database with the help of the ODBC connection it displays an Error 3146- ODBC Call Failed. The database has been set as a source of data for the system with the driver of SQL Server.

Hence on launching the .mdb application database could be attached and results are fetched. But while populating data on the combo box, it shows ODBC call failed error 3146.

This error report is actually the hexadecimal format of the error code that’s generated. This is frequently brought into usage by the MS Windows along with additional compatible software and drivers. In some cases you may find superfluous constraints into the 3146 ODBCl failed Access error. The further letter and number code are addressed onto your storage fragment where all instructions are being saved at the time of happening of this error message.

Cause For Run Time Error 3146 ODBC Call Failed Access Error Code?


As discussed the major reason for the run-time error 3146 to happen is the corruption of the Windows system files. Because if the entries of the system are broken, then it is enough two pose considerable injury to the overall health of the individual computer system

Some well-known reasons for the cause of this error include fragmentary installation, erasing a fractional file, inappropriate removal of equipment and software. Even attack of some malicious programs like Trojan or other virus-like spyware or adware could lead to this hectic situation. And these entire instances are sufficient for deleting or corrupting system files of the Windows. The damaged file will let you in wrongly and missing linkage of details and data files that are vital for the program to function correctly.

Fixes To Resolve MS Access Run-time 3146 ODBC Call Failed Error

Record Locking Errors in Microsoft Access applications

Method 1: Remove ODBC 1.x Driver Manager

To fix this issue it is advised to remove the ODBC 1.x Driver Manager (Odbc.dll) and replace it with ODBC 2.x Driver Manager (Odbc.dll) in the primary path.

Method 2: Advanced Computer User Resolution (advanced):

  • Turn on your system and run as an administrator.
  • Go to the start button and go for All Programs, Accessories, System, and after that opt for System Restore.
  • Commencing subsequent screen, press “Restore my machine to a previous time” and then hit NEXT.
  • Locate mainly present restore point inside the “select a restore date” list, and click Next after that.
  • On verification screen of system click Next.
  • When restoration is done, Reboot the system.

Fully Automated Solution:

If all the above-mentioned solution does not help to fix this issue then I would suggest opting for a third-party tool that solves any sort MS Access related error. And the best available tool for this purpose is MS Access Repair and Recovery Tool.

This tool is not only fixed errors but also fixes the .mdb or .acccdb files and recovers the data from your corrupted MS Access database.  You can also restore the indexes, tables, queries, and relations very easily by using this tool.

* By clicking the Download button above and installing Stellar Repair for Access (14.8 MB), I acknowledge that I have read and agree to the End User License Agreement and Privacy Policy of this site.

Steps To Fix MS Access error 3146

Wrap Up:

Above listed fixes will surely resolve MS Access error 3146: Run-time 3146 ODBC Call Failed. Do try all the solutions and let us know whether it worked for you or not.

If you are facing any other issue in your access database then ask your queries on our social account likeFacebook and Twitter.

tip Still having issues? Fix them with this Access repair tool:

This software repairs & restores all ACCDB/MDB objects including tables, reports, queries, records, forms, and indexes along with modules, macros, and other stuffs effectively.

  1. Download Stellar Repair for Access rated Great on Cnet (download starts on this page).
  2. Click Browse and Search option to locate corrupt Access database.
  3. Click Repair button to repair & preview the database objects.

Pearson Willey is a website content writer and long-form content planner. Besides this, he is also an avid reader. Thus he knows very well how to write an engaging content for readers. Writing is like a growing edge for him. He loves exploring his knowledge on MS Access & sharing tech blogs.