Microsoft KB Archive/920767

= You may receive an error message when you use a localized ODBC driver in your application on a Windows Server 2003-based computer or on a Windows XP SP2-based computer =

Article ID: 920767

Article Last Modified on 2/15/2007

-

APPLIES TO


 * Microsoft Data Access Components 2.8
 * Microsoft Data Access Components 2.8 Service Pack 1
 * Microsoft Data Access Components 2.8 Service Pack 2

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
Consider the following scenario. You use a localized ODBC driver in your application. For example, you use the Spanish version of ODBC driver Microsoft ODBC para Oracle. You run the application on a Microsoft Windows Server 2003-based computer or a Microsoft Windows XP Service Pack 2 (SP2)-based computer. In this scenario, you receive the following error message in your application:

ODBC error connecting with Microsoft ODBC para Oracle



CAUSE
This problem occurs because the registry subkey of the localized ODBC driver does not exist on a computer that has Microsoft Data Access Components (MDAC) 2.8 or a later version of MDAC installed.

The later versions of MDAC do not include the localized versions of the ODBC driver. MDAC 2.8 is included with Windows Server 2003 and Windows XP SP2. Therefore, you cannot run the application that uses a localized ODBC driver on a Windows Server 2003-based computer or a Windows XP SP2-based computer.



RESOLUTION
To resolve this problem, follow these steps:
 * 1) Modify the application to use the English version of the ODBC driver.
 * 2) Update the computer that has earlier versions of MDAC installed to MDAC 2.8 or a later version of MDAC.



WORKAROUND
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

If you cannot modify the application, you must modify the registry to work around this problem. To do this, follow these steps on the computer on which you experience this problem.

Note These steps assume that you use the ODBC driver Microsoft ODBC para Oracle in your application.  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

 Right-click the registry subkey, and then click Rename. Type Microsoft ODBC para Oracle as the new name of the registry subkey. Locate the Microsoft ODBC for Oracle registry entry under the following registry subkey:

 Right-click the registry entry, and then click Rename.</li> Type Microsoft ODBC para Oracle as the new name of the registry entry.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="references_section">