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

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?

You are probably careful to avoid doing this, but all versions of Access have a fairly good chance of corrupting the code project if a form/report's code is edited in any way without going to design view first.

If you are editing a form's code with the form in form view, then it looks like SP1 raised the chance of corruption to 100%.

No, I wasn't aware of that. But I never had this problem in earlier versions.

What do you mean by " it looks like SP1 raised the chance of corruption to 100%."

You are probably careful to avoid doing this, but all versions of Access have a fairly good chance of corrupting the code project if a form/report's code is edited in any way without going to design view first.

If you are editing a form's code with the form in form view, then it looks like SP1 raised the chance of corruption to 100%.

Strongly agree Darrell, and thanks for this very helpful update, particularly the confirmation that the decompile workaround is not a permanent or a realistic solution in a client context.

Since uninstalling SP1 here, everything has been functioning normally across all apps. We can only hope that Microsoft is monitoring this real-world experience with SP1 and is urgently working on a revised SP1 (or at least a reliable fix).