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

You said that every code change caused you to do a decompile the next time you open the db so it sounds like it always corrupts (i.e. 100%).  In my experience, editing code in form view corrupted the code project about 20% of the time (seemed to go up with the amount of code).  So, if you are not going to design view before editing code, the odds went up from about 20% to 100%.

If you always go to design view before editing code, then you are seeing a new problem.

 

The developers who you are getting these bug reports from are not doing silly things. We are simply trying to do the core tasks of developing and amending database code and components as we have all done for years without problems. Access 2010 was great, totally reliable and an excellent development environment, UNTIL SP1.   If we uninstall SP1, we are again without problems. What does it take to get this message and its logical implication across, together with a sense of the urgency of the issue for Ac cess 2010 developers?

My thoughts EXACTLY!  Thanks.

I want to add that I also found this in a DEVELOPER context. I built a pivot chart report and it was working fine. I then compacted/repaired the database and it wouldn't open. Each time it just gave me a message that Access encountered and error and was closing.  I went to the Event Viewer and the above error showed up.

I did not figure out it was related to this until much later.  I opened the db on another 2010 machine and it worked fine.  Then I "repaired" my Office 2010 installation and now it is working on this machine again. 

I wanted to add to those who have reported to insist that Microsoft get this resolved asap.  I develop Access dbs for a living and this issue is killing my productivity.  Please advise us on your progress.

Thanks

1. Having developed databases in Access since Access97, I always go to design view first out of habit and good practice, even though it is no longer strictly necessary (or should I say until SP1 it was not necessary)
2. If you open in design view a simple form that has been running normally and developing code normally for months under pre-SP1 vbe7.dll, and then add even limited code (such as a simple for-next loop to clear a list), then under SP1 this triggers a crash.
3. You also get crash VB-related problems in a vital developer context where you are developing new or amended database components in the master copy on your computers, and then either sending them out to clients or dealing with the integration of the new elements through a mixture of import/export and/or remote access.

The SP1 pre-release testing apparently neglected to check the developer context, where a developer was needing to add code to an existing form or module. Existing accdbs will usually run OK providing that you don't try to develop them. This is presumably why you are getting fewer problems with users of existing systems, and the main focus of problems is in the development context.

The developers who you are getting these bug reports from are not doing silly things. We are simply trying to do the core tasks of developing and amending database code and components as we have all done for years without problems. Access 2010 was great, totally reliable and an excellent development environment, UNTIL SP1.   If we uninstall SP1, we are again without problems. What does it take to get this message and its logical implication across, together with a sense of the urgency of the issue for Ac cess 2010 developers?