Database table considerations

  • You should only install a single language pack to a particular database. In theory, you can install multiple language packs into a single database. Because Optiva descriptions only support a single language (for objects like Parameters, Set Codes, etc.), it is generally only practical to support a single language per Optiva database
  • Available language codes must be defined in the FSLANGUAGE table. The codes must be valid Language Codes in the FSCULTUREINFO table.
  • For the web client, the language code is determined by Infor Ming.le or the browser. If Optiva is running outside of Infor Ming.le, then the language code is determined by the browser.
  • When a language code is added to the FSLANGUAGE table, a column is displayed in the Enumerated List form for the corresponding language code.
  • Labels for forms and form controls (tabs, title, menu, tool tips, function buttons) by language are stored in the FSWEBLABEL table.
  • Labels for form fields are stored in the FSFIELDLABEL table.
  • In the web client, you can use the Field Label form to configure grid labels in different languages.