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

Nathan,

Thanks and appreciated. In this exceptional situation, we would all be very grateful if you could specifically ask the KB team to include a separate section with instructions covering the **'SP1 has been uninstalled'**situation.  This would avoid potential complications for everyone, and help smooth the transition back to a standard state for all users and developers.

Here's another bizarre 'error' that I stumbled upon.  A guy by the name of Hellion found the 'solution.'

MS is killing us with this stuff.

Here's what I finally found out that appears to be relevant:

On 64-bit Windows 7 Pro, the Microsoft MDAC Component Checker tool tells me that I am running MDAC version "UNKNOWN", with file versions of either 6.1.7600.16385, or 6.1.7601.17514 (which by a strange coincidence match up very closely with the Windows version number). On 32-bit Windows XP, on the other hand, Component Checker says I'm running version "MDAC 2.8 SP1 ON WINDOWS XP SP3", with file versions of 2.81.1132.0 or 2.81.3012.0, which look like proper MDAC version numbers.

If I change the "broken" code while I'm on XP and thereby force a recompile, the exact same code that produced the run-time error (either the type mismatch 13 error mentioned above, or a run-time error 430) will start working (and keep working when I copy it around to other XP boxes, or to my Windows 7 box). If I change the code on my Windows 7 box and redistribute that to an XP box, it breaks, despite the fact that every reference in the list of references is identically named, and points to an identical file in an identical disk location.

Edit: Apparently this version numbering is due to Windows Vista/7 using "WDAC" instead of "MDAC", and the specific problem of code compiled on Win7 SP1 being broken when run on downlevel OSes is a known issue, referenced at support.microsoft.com kb article 2517589 and at this post on technet. Switching to late binding, installing a KB fix on the downlevel systems, or linking in "back-compatible" versions of ADO are the suggested fixes.

Edit 2: The fix that I have settled on at this point is to go ahead and do all my development work (with early binding) on my Win7SP1 box, and then recompile the whole app on a WinXP box before deploying it to my users.

Hi Jon,

Once a fix is released, the corresponding KB article for that fix usually lists the steps you need to go through in order to install the fix and it should also list the pre-requisites for the fix.  At this time, I don’t know the exact process you will need to go through, but once a fix is released the KB article should have that information.

Best Regards,

Nathan O.

Microsoft Online Community Support

Nathan,

For the avoidance of doubt, does this mean that all those who have uninstalled SP1 during the last 2months will now have to install SP1 again and then immediately install the cumulative update?  Would both updates be able to be installed in a single pass of MS Update, or would two passes be needed in order to allow SP1 to be installed first?

As you can imagine, the practicalities of arranging the timing of the SP1 and then the cumulative update both for our own systems and for all of our clients will require quite clear advice and organisation in advance to avoid any further problems. 

It would be appreciated if you could confirm exactly what stages would need to be completed for users who have uninstalled SP1