Real quick one today, one of my users today told me she had been holding off upgrading to Office 2010 SP1 due to an error using one of the Wizards in Access 2010.
She happened to be on x64 but I believe this was a bug in both.
Error Details:
"The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from modules, forms and reports. You should back up your database before attempting to open the database and delete the VBA project."
Once you click OK on this message, you may receive any of the errors below:
Cannot update. Database or object is read-only.
ORThe Visual Basic for Applications project in the database is corrupt.
ORMicrosoft Access can’t find the wizard. This wizard has not been installed, or there is an incorrect setting in the Windows Registry, or this wizard has been disabled.
Well all you need to do to fix it is get the hotfix from Microsoft:
http://support.microsoft.com/default.aspx?scid=kb;en-US;2581301
Just simply scroll down to the large consumer focused icon that say "Microsoft Fix It" and click it. You download a quick package which patches Access.
Note: Make sure you close down all of Office first!
Enjoy,
Eric
That fix does not work on Win 7 64B with Access 2010
Have you tried fixing it manually?
1. Close all instances of Microsoft Office Access 2010.
2. Rename the appropriate wizard files located at c:\Program Files\Microsoft Office\Office14\ACCWIZ\ or c:\program (x86)\Microsoft Office\Office14\ACCWIZ depending on which version you installed.
Original File Name Rename To:
Acwzmain.accde Acwzmain.old
Acwzlib.accde Acwzlib.old
Acwztool.accde Acwztool.old
Note: Before renaming files, ensure file extensions are visible. To learn more about this, view the following:
To fix databases you may use next software.
Access Fix Toolbox restores access databases in cases: database cannot be opened or read, .mdb file is corrupted and so on.
Thanks for the info – just applied the hotfix and it resolved the error.