Access 2010 SP1 – You receive random crashes in certain database or when opening the VBA window in those databases after installing Office 2010 SP1

Thanks Nathan & JonFarmer.  Yes, I did wipe the 2003 and 2007 components with the utilities, including MSO2010, then re-installed MSO2010 before posting here.  I will check the vbe7.dll versions at home/work and report back here.  I did find out today that another person had the same problem as I last year, but didn't report it nor document what resolved it.  They have SP1 installed and are not having any problems at this time -- these would be clean installs on wiped/new drives.

Hi Jwhite_NC,

Unfortunately, I don’t think the issue you are experiencing is related to this specific SP1 issue or even the other SP1 issues.  If this is happening for all databases on your machine, including any new databases you create, then you may have something else wrong with your base Access 2010 install (perhaps causes by the side by side Access installs on your machine).  If you have your media and product key for Office 2010, you may want to run the utilities in the article below to completely remove your Office 2007 components and then your Office 2010 components.  I would also have you run the utility to remove the Office 2003 components, but if you only had Access 2003 standalone installed, this may not work, since I believe it only works on suites.  After you run this utility for Office 2007 and Office 2010, I would then recommend installing Office 2010 again.

290301            How do I uninstall Office 2003, Office 2007 or Office 2010 suites if I cannot uninstall it from Control Panel?

http://support.microsoft.com/default.aspx?scid=kb;EN-US;290301

If you still have problems after doing this, I would recommend probably creating a support case with Microsoft, so that we can look at it with you. 

Online Assisted Support Options (create cases online) - http://support.microsoft.com/select/default.aspx?target=assistance

Best Regards,

Nathan O.

Microsoft Online Community Support

Understand, and we have all had this feeling for several weeks now.  What might help slightly to clarify the factors involved in your particular context would be if you could check the version number for your vbe7.dll files on your home computer and at work. It is possible that there is a discrepancy which is causing you additional problems, particularly if you have taken accdb files between machines and then compiled them (e.g. auto compile on close) while they were in the other machine. If you do a file search and then check whether the vbe7.dll version is 7.0.16.19 (after SP1) or 7.0.15.90 (pre SP1)  the discrepancy may have contributed to this additional hassle.

There is no real solution until MS put out the Fix or an amended SP1, but the additional problem of a discrepancy between home and work systems is one which we are all now having to face.

Sadly I installed Office  Pro 2010 and the results brought me here - same issue.  However, I have not applied SP1

Version: 14.0.4760.1000 (32-bit)

OS: Vista

Hardware: 64bit

EDIT:  Clicked Additional info link and MS-Access is 14.0.4750.100

ANY database opened gets the "...VBA project contained in it cannot be read...." message.  INCLUDING MS-Access example .ACCDB databases!  My job has had 2010 installed now for a year and never experienced it at work.  Now, on my computer with my purchased copy, sadly, I get the error.

MS Office Pro 2007 and MS Access 2003 were installed prior to the upgrade.  Thinking the older versions were the culprit, uninstalled any leftovers, uninstalled MSO2010, reinstalled, and the problem did not go away.

/decompile does not help.

Created a NEW database, then clicked Ctrl-G, and the error occurred again.

While my programming at home isn't my bread-winner like most here, it is preventing me from getting side-work payments for projects that were near ready for release.  Now I can't do anything unless I uninstall MSO2010 and put MSO2007 and MSA2003 back on?  Nuts...