Microsoft KB Archive/168894
Article ID: 168894
Article Last Modified on 10/3/2003
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q168894
BUG #: 16486 (NT: 6.50)
If you use the French Client Configuration Utility to check or clear the 'Conversion ANSI -> OEM automatique' (the French equivalent of 'Automatic ANSI to OEM' in the English client) option, clients behave as if you never did.
Instead of writing the value (on or off) in the AutoAnsiToOem registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSqlServer\Client\DB-LIB, the Client Configuration Utility creates a new key called 'Conversion ANSI-OEM automatique' under the same path and writes in that newly created key.
Use either Regedt32.exe or Regedit.exe to directly edit the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSqlServer\Client\DB-LIB \AutoAnsiToOem, and set the value to on or off.
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
When the client is first installed, it has two registry keys, AutoAnsiToOem and UseIntlSettings, under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSSqlServer\Client\DB-LIB as usual. The value for AutoAnsiToOem in the registry is set to On; however, in the Client Configuration Utility, the 'Conversion ANSI -> OEM automatique' check box is clear. Once you place a check in it, it creates a new registry key called 'Conversion ANSI-OEM automatique' and sets its value to On. Toggling this check box toggles the value on and off for this new key.
All the DB-Library clients use the AutoAnsiToOem key and not the 'Conversion ANSI-OEM automatique' key to determine whether or not they should perform ANSI to OEM conversion. Therefore, clients like ISQL and ISQL/w do not reflect the change made by Client Configuration Utility for the 'Conversion ANSI -> OEM automatique' check box.
For more information about ANSI to OEM conversion, please refer to the following article in the Microsoft Knowledge Base:
153449 : INF: SQL Server Code Pages and AutoAnsiToOem Behavior
Keywords: kbbug kbusage KB168894