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.
Contents
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 you want to execute each time a button clicks. 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
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 this error is that MS Access does not trust the database from which the macro is run. By default, Access opens databases that are not trusted in the Disabled mode. In the Disabled mode, executable content is disabled, preventing you from running a macro.
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
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.
Note: Repeat these steps 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 to move the database. To do so, perform the following steps:
- In MS Access, click the File tab and then select Options.
- From the ‘Access Options’ dialog box, select Trust Center > 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.
Once you have the trusted locations list, move the Access database to anyone 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 pIn none of the above methods works for you, consider using an Access repair tool like Stellar Repair for Access to repair your database (MDB/ACCDB) files and restore macros. Download the free demo version to preview the recoverable macros and other objects before saving the repaired file.
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 and its objects without downtime.
in my case, the error came on the macro called by a “find a record on the form based on a listbox”. The error occurred after I added code in the form_load event to select an item from the list. Funny thing, it worked initially, but after I closed and reopened the database it would fail on form load, but would work after that which was the clue that allowed me to fix it. I moved the code to select an item to the form_Activate event instead of form_load and it worked properly.
Aw, this was an exceptionally nice post. Spending some time and actual effort to create a superb article like this.
Hi,
I am having this issue on a new computer. The database works just fine on the old database but I get this error when opening it on the new computer.
I have done all of the above. I have uninstalled and reinstalled. Any other thoughts?
TY
In my case the issue came from a formula on a report =IIF([field]=”2″,0,1) my field was a number field which caused the 2950 error. The fix is =IIF([field]=2,0,1) (this was to count a specific value later on.)
In my case, Shifting the Un-Trusted Data to a Trusted Location helped me to fix all things smoothly.
Feeling great! Solved my error using free tips.
Good!
You can also subscribe to our blog for receiving the latest tips & tricks.