OpenROAD 6.0 applications using Enterprise Access 2.7 or later for Microsoft SQL Server behave differently than OpenROAD 5.1 does while using Enterprise Access 2.6.

Enterprise Access 2.7 and 3.0 support Unicode, so OpenROAD 6.0 will send it bind parameters as nvarchar strings. It also sends string literals in SQL statements as nvarchar bind parameters.

OpenROAD 6.0 will send bind parameters to Enterprise Access as nvarchar strings only if the configuration of Enterprise Access is Unicode enabled. It is not possible to configure Enterprise Access 2.6 to be Unicode enabled.

All Unicode strings returned from Enterprise Access 2.7 and 3.0 are nvarchar. This includes the Unicode strings that Enterprise Access receives from MS SQL Server functions. This was not the case with prior releases of OpenROAD using Enterprise Access 2.6; they converted Unicode strings from SQL functions to the local character set.