Mertech’s drivers have a standard OEM to translation based on the Windows API. When this feature is enabled, data sent to the SQL database is translated from the OEM to ANSI Character set and from ANSI to OEM before the data is sent back to the application.
The new version 11 drivers have a new feature available that allows the user to customize the mapping value for the OEM to ANSI translation. Basically the user can customize the OEM and the ANSI Character Translation using a macro command or through the mertech.ini file entry. The difference between these two approaches it is that the macro command must be added to each application, which means that some code has to be added and then the application source code has to be recompiled. But on the other hand, the use of the mertech.ini introduces the use of the Custom OEM to ANSI Character Translation automatically when the INI file is read during the driver initialization.