How to Fix MS Access Database Error 2950?

Summary: This blog discusses about Microsoft Access database error 2950. It explains the reasons behind the error and manual methods to fix it. You can also try using Stellar Repair for Access software to restore your database with all its data intact.

How to Fix MS Access Database Error 2950?

About Microsoft Access Database Error 2950

A macro is a useful tool in MS Access. It helps automate tasks that you often perform in a database. For instance, a macro may contain commands that you want to perform each time a button gets clicked. However, scripts that make the execution of macros possible can easily get corrupted and cause unexpected errors. “Action Failed Error Number: 2950” is one common error you may encounter when running a macro in an Access database. The complete error message reads as:

Action Failed
Macro Name: MacroName
Condition: Condition
Macro Name: RunCode
Arguments: Arguments
Error Number: 2950

Macro Failed error
Fig 1 – MS Access Macro Error 2950

Primary Reason Behind Access Database Error 2950

MS Access Error 2950 is received when a macro calling a Visual Basic for Applications (VBA) function is run in MS Access database 2007 or higher. The primary reason behind the occurrence of this error is that the database from which the macro is run is not trusted by MS Access. By default, Access opens databases that are not trusted in the Disabled mode. In the Disabled mode, executable content is disabled.

Methods to Troubleshoot Microsoft Access Database Error 2950

To fix the Access macro error 2950, try enabling the database by following any of these methods:

Note: Before trying these methods, you must first determine if you can trust the database.

Method 1 – Enable the Database for Current Session

This will enable the database only for the current session. The database will be disabled as soon as you initiate a ‘Close Database’ command. Follow the steps below:

  • Open your Access database. From the ‘Security Warning’ message bar, click on Options.
  • When ‘MS Office Security Options’ dialog box opens, click on Enable this content and then click OK.
Enable Microsoft Macro Content
Fig 2 – MS Office Security Options

Note: These steps should be repeated each time you open the database.

Method 2 – Move the Database to a Trusted Location

Before moving the database, you must first find out the trusted locations on your system where you can move the database. To do so, perform the following steps:

  • In MS Access, click the File tab and then select Options.
Access options
Fig 3 – Access Options
  • From the ‘Access Options’ dialog box, select Trust Center > Trust Center Settings.
Access Trust Center Settings
Fig 4 – Microsoft Access Trust Center Settings
  • Click Trusted Locations and then do any of the following:
    • Note paths of the trusted locations listed under ‘User Locations’.
    • Add a new trusted location. For this, click on Add new location, and then specify the path of the location that you want to add.
Trusted Locations
Fig 5 – Select Trusted Locations

Once you have the trusted locations list, move the Access database to any one of them.

What to do if the Error Persists?

In case you’re unable to perform any of the above-mentioned fixes or the problem still persists, there may be an issue with your database files. In such situations, use Stellar Repair for Access software to repair corrupt MDB and ACCDB database files, and restore macros, forms, queries, and other objects. The software also supports recovery of linked tables, calculated data types, and can retrieve password-protected forms and modules.

free download

Final Thoughts

Every problem has a solution, especially if you have the right kind of help. You may find it easy to troubleshoot the error 2950 in Access database manually. However, at times, troubleshooting the error manually can be tricky and might fail to make the database accessible. But, leveraging a secure and reliable Access repair software, such as Stellar Repair for Access can help you restore the database without downtime.

  1. Dave March 1, 2020
  2. Lavis brown September 26, 2019
  3. Frank August 25, 2019
  4. Lloyd Thiessen August 23, 2019
  5. Mike Moore April 16, 2019
  6. Michael January 7, 2019
    • Eric Simson January 8, 2019

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.