Unicode vs. ANSI Databases - Unicode Considerations - English - Foundation 22.1 - OnBase - external

Unicode Considerations

Unicode Considerations
Foundation 22.1

Prior to OnBase 13, OnBase only supported ANSI databases, each of which is limited to the group of languages included on the single code page it is configured for. To ensure proper functioning of the software in a desired language, administrators would have to specify a code page that supports this language at both the Windows level and the database level. Because ANSI databases can only be set to use a single code page at a time, however, they do not provide a good way for organizations to store data across multiple languages when those languages are not supported by a single code page.

Beginning in OnBase 13, OnBase provided limited support for Unicode databases for new customers planning to upgrade to fully functional Unicode systems in OnBase 14 or later. While these customers still did not have access to Unicode functionality in OnBase 13, they had the option of initially creating a Unicode database that would readily support Unicode functionality upon upgrading to OnBase 14 or later, as opposed to initially creating an ANSI database and then converting to a Unicode database when upgrading.

As of OnBase 14, OnBase provides optional Unicode support for multiple code pages in the same database. This change will not affect the majority of OnBase users who upgrade to OnBase Foundation 22.1 since it pertains only to customers who request a Unicode database. By default, OnBase Foundation 22.1 databases will continue to be single-code page ANSI databases.

For customers moving to OnBase Foundation 22.1, the following scenarios are possible:

  • Existing OnBase users who upgrade and intend to operate within the single-code page limitation of ANSI databases will not have to do anything to their databases in preparation for the upgrade. After the upgrade, their systems will continue to function as they always have in conjunction with the single code page specified for the database.

  • Existing OnBase users who already created a Unicode database in OnBase 13 will not have to do anything to their databases in preparation for the upgrade. After the upgrade, they will have access to all currently supported Unicode functionality.

  • Existing OnBase users who are still on ANSI databases and have an immediate or anticipated need for multi-code page database support will need to contact Database Support to facilitate a significant manual conversion of their existing ANSI databases to Unicode.

  • Customers installing new OnBase systems with OnBase Foundation 22.1 who have an immediate or anticipated need for multi-code page database support may elect to create a Unicode database, which will give them access to all currently supported Unicode functionality.

After upgrading, existing OnBase users who converted from ANSI databases to Unicode databases must access OnBase from the current, Unicode-supported version of the software; they cannot continue to access OnBase from older versions of the software that only supported ANSI databases.

With only the exceptions noted below, the entirety of the OnBase product suite will support multiple code pages in the same Unicode database. Modules that are not compatible with Unicode databases will not operate if the system detects a Unicode database. These are generally modules that have had their End-of-Life status listed for one or more years already.

If you believe you will be affected by this change, please contact your support organization to make sure Hyland Software is aware of your needs. The conversion of an ANSI database to a Unicode database is not a trivial undertaking and may require planning tailored to your specific needs.