An ADO-based application that is compiled in Windows 7 SP1 or in Windows Server 2008 R2 SP1 does not run in earlier versions of Windows

Assume that you develop an ActiveX Data Objects (ADO)-based data access application on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1). However, the application does not run on a computer that is running an earlier version of Windows.

Notes

• ADO-based applications that are compiled in Windows 7 SP1 or in Windows Server 2008 R2 SP1 use the new interface identifiers (IIDs) in the ADO type libraries that were included in the SP1 packages for Windows 7 and for Windows Server 2008 R2.
• This issue does not occur if the hotfix that is described in the following Microsoft Knowledge Base article is installed on the computer that is running an earlier version of Windows:
  983246

  (http://vkbexternal.partners.extranet.microsoft.com/VKBWebService/ViewContent.aspx?scid=KB;EN-US;983246)

  "Type Mismatch" error message when you run a VBA macro in a 64-bit version of an Office 2010 application

Assume that you compile a VB6-based or VBA-based application that is compatible with versions of Windows that are earlier than Windows 7 SP1 and Windows Server 2008 R2 SP1. After you install this update, Visual Basic automatically displays the Microsoft ActiveX Data Objects 6.1 Library in the Available References list when you try to add references to the current project. To manually locate the ADO 6.0 type library (Msado60.tlb) in this situation, browse to the following location:

%program files%\common files\system\ado

Notes

• Visual Basic automatically displays the ADO 6.0 type library in the Available References list if the reference to the ADO 6.0 type library was added to current project.
• Consider the scenario where you are a C++ developer, and you include the following line of code in the application:

   
  #import msado15.dll
  

  
  Consider the scenario that you recompile an application that must run in Windows Vista, in Windows Server 2008, or in later versions of Windows. And, you are not using MSJRO. In this scenario, you must change #import msado15.dll to the following:

   
  #import msado60.tlb
  

  
  Consider the scenario that you are using MSJRO, and you recompile an application that must run in Windows Vista, in Windows Server 2008, or in a later version of Windows. In this scenario, you must change #import msado15.dll to the following:

   
  #import msado28.tlb
  

  
  Consider the scenario that you recompile your application that must run in Windows XP or in Windows Server 2003. In this scenario, you must change #import msado15.dll to the following:
  

  #import msado28.tlb

• 
  If you are a C++, VB6, or .NET developer and if you applied "Method 1" in the "Workaround" section that was described in Microsoft Knowledge Base (KB) article 2517589, you do not have to change the code. (Note that this workaround was removed after update 2640696 was released). However, we recommend that you install this update to make sure that the ADO interfaces on your computer are up to date.
  
  For more information about KB 2517589, click the following article number to view the article in the Microsoft Knowledge Base:
  2517589

  (http://support.microsoft.com/kb/2517589/ )

  An ADO application does not run on down-level operating systems after you recompile it on a computer that is running Windows 7 SP 1 or Windows Server 2008 R2 SP 1 or that has update 983246 installed

How to obtain this update

The following files are available for download from the Microsoft Download Center: For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To apply this update, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Registry information

To use the update in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

File information

The global version of this update installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

• The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
  Collapse this tableExpand this table

  Version	Product	SR_Level	Service branch
  6.1.760 1 . 17xxx	Windows 7 and Windows Server 2008 R2	SP1	GDR
  6.1.760 1 . 21xxx	Windows 7 and Windows Server 2008 R2	SP1	LDR

• GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

For all supported IA-64-based versions of Windows Server 2008 R2

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Additional files for all supported IA-64-based versions of Windows Server 2008 R2