A family of Microsoft relational database management systems designed for ease of use.
This did not help, still get the same errors.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am getting the "The database cannot be opened because the VBA project contained in it cannot be read" error on anything I try to work with, including the Northwind 2007 database. If I open an existing query or table, I get that error, sometimes repeated more than 40 times. It also occurs if I try to "Compact and Repair". I have seen many references to this error but nothing that I have been able to tie to my situation. I believe it may have started when I uninstalled an unwanted trial version of Office 2016. Any suggestions are appreciated. I don't work with Access very often, but was trying to help a charitable organization with their database.
Office 2010 Pro SP2 version 14.0.7194.5000 running on Windows 10.
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This did not help, still get the same errors.
This problem is discussed in detail here:

It offers a wizard that if run, supposedly fixes the problem.
This section offers a more detailed description of the issue:
Regards,
Al
Office Repair did not help.
No, I never used 2016. Word and Excel would try to default to 2016 but it would then ask me to to license it.
I had tried a blank database, but the import would fail - couldn't select what to import without getting the same error.
I should have mentioned that I had also uninstalled Office, rebooted, then re-installed Office.
I think I had run Office Repair, but I'll try it to make sure, and report back.
Is it possible that you did do some work on the database with the 2016 trial version?
Have you tried an office repair?
What about trying to create a new blank database and then trying to import objects from the version that is not working properly?