| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Translator Specification Subkeys |
Translator Specification Subkeys |
David-Engel |
davidengel |
01/19/2017 |
sql |
connectivity |
conceptual |
|
Each translator listed in the ODBC Translators subkey has a subkey of its own. This subkey has the same name as the corresponding value under the ODBC Translators subkey. The values under this subkey list the full paths of the translator and translator setup DLLs and the usage count. The formats of the values are as shown in the following table.
| Name | Data type | Data |
|---|---|---|
| Translator | REG_SZ | translator-DLL-path |
| Setup | REG_SZ | setup-DLL-path |
| UsageCount | REG_DWORD | count |
For information about usage counts, see Usage Counting earlier in this section.
Applications should not set the usage count. ODBC will maintain this count.
For example, suppose the Microsoft Code Page Translator has a translation DLL named Mscpxl32.dll, that the translator setup functions are in the same DLL, and that the translator has been installed three times. The values under the Microsoft Code Page Translator subkey might be as follows:
Translator : REG_SZ : C:\WINDOWS\SYSTEM32\MSCPXL32.DLL
Setup : REG_SZ : C:\WINDOWS\SYSTEM32\MSCPXL32.DLL
UsageCount : REG_DWORD : 0x3