Error: The Personnel and Passenger records within FOS do not save specific language keys

Error: The Personnel and Passenger records within FOS do not save specific language keys

Error:
The Personnel and Passenger records within FOS do not save specific language keys, such as: Ä/Ö/Ü/ß


Solution:
If a FOS customer is using another language and are unable to save data with foreign letters, the below function will need to be applied.

The Registry Key must be adjusted with the following:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Titan\Btrieve\CONFIGURATION\Intl]
"IgnoreAnsiOEM"=dword:00000001
"IgnoreOEMAnsi"=dword:00000001

After application of the registry key, the users will be required to log out and log back in.

    • Related Articles

    • Error: Illegal characters in path.

      Error: Illegal characters in path. Solution: Within the Report Name field, remove any special characters. If you are using characters to bring your report to the top of the selection list, please use numbers instead.

    • Language Tab

      The Language Tab can be used to enter in the different languages spoken at the specific airport. This information is manually entered by a user. Select the red "+" to add. You can view the various language codes by selecting the language box.

    • Email To SMS Email Address List

      You can send an email from FOS to be received as SMS. To do so, any text message field (user, personnel, passenger, etc) needs to be configured with the phone number + carrier extension from the list below. US & Canadian Carriers 3 River Wireless ...

    • Error: Access violation at address 00B78CC7 in module 'Fos.exe'. Read of address 00000069. in the Personnel and/or Passenger module

      Error: Access violation at address 00B78CC7 in module 'Fos.exe'. Read of address 00000069. when selecting the Personnel module Solution: Open the convert utility and run the FmUpdate.btr convert for 3.11.9.0

    • Access violation when running personnel report

      If a user tries to run a personnel report, from the personnel module, on either an individual crewmember or multiple selected crews, they may encounter the below access violation error. The solution for this is to go to the Operations board, choose ...