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

Just an update to the above reply; when I uninstalled the SP1 update, and the vbe7.dll went back to the previous version, I can now open code pages and the whole accdb functions as normal again. So the bug is specific to SP1. I have switched off automatic updates and will wait until Microsoft confirm that they have issued an amended SP1 or a fix.

Hi Jon,

 

Did  you try the workaround mentioned above?  After decompiling the application with SP1 installed, it should then work successfully.

 

Best Regards,
Nathan O.
Microsoft Online Community Support

Some have already tried this and it did not work for them. In our case, as with some of the other people who have been having SP1 problems on the forums, this won't work for us  because we have a number of users of various levels of expertise distributed round the UK and we certainly can't expect them to go through decompiling and recompiling existing versions of the system. We cannot at present even send them updates by email because they cannot open them owing to the VBA problem.

The key point is that Microsoft have put out a Service Pack which is faulty in a really important area; you cannot expect users to have to decompile all their existing databases before they can use them or develop them. We have perhaps 20 different Access 2010 databases dealing with different functions; are we supposed to decompile all of them before we can use them? 

The SP1 is faulty and it needs fixing urgently; can you please arrange for a notification when the amended update or fix is ready, and we can then try to organise a coherent way out of this mess. It is holding up work and costing us delay money.

Jon

I'd like to append my comments to Jon's. I develop Access apps for my livelihood and it does me no good to explain to my clients that "Microsoft is aware of this problem". In their eyes, I am at fault for installing a broken program on their machines, and I have to fix it.

This is an urgent matter.

Darrell

BTW, Jon, another member submitted this issue in a different forum back in February, and he discovered that removing the "Send to Bluetooth" COM add-in solved his problem. Have you tried this?

Darell,

Thanks very much for this suggestion, but given our range of database users with different levels of expertise we have to stay with a default system (and any modifications could perhaps come back to bite at some point in the future?).  Microsoft have the resources to check SP1 across the full range of Office 2010 applications as well as Access, so we really need their help to rectify this fault now that it has been notified.

Jon

Hi Nathan

 

Thank you for the workaround which recovers what appeared to be a completely corrupted database.  This has caused me days of angst and extra work at one client in particular.  As a Microsoft Partner developing Access databases as my core business this is a hugely embarrasing flaw in the Microsoft Access Product and I trust the fix will be available soon and delivered via WSUS?

 

Many thanks in advance

Best wishes

Graeme Whyte

Nathan,

I did the decompile yesterday and it immediately bounced back. So far so good. I'll keep my eye on it.

Darrell

Yes, i definitely had this problem and it does seem to be connected with the compilation state.

I always have 'compile on Demand' turned off and I get the crash if i have made a code change and forgot to check that it compiles correctly before closing the database.  When i reopen it, it crashes on re-opening.

This suggests it may be mitigated by having 'Compile on Demand' turned on :) but it is always best to see the code compiles before you shut the database.

Since checking that everything compiles okay before i close it, i have not had the problem.

Mike