Hi,

I have come accross an issue where special characters such as Ñ, Ø etc are not supported primarily in the primary keys or index fields. This issue can be resolved as follows:

1 Go to $BSE\lib\DEFAULTS\all
2. Check if following line is there in file. If not add/modify
high_ascii_tolerance:1

Hope it will help others and save lot of time in identifying the cause.

Cheers !!
Davendra

The information is available in the Bugfixes_for_Porting_Set_84a

DevChopin: # 34446 (BDUX26484): set.fmax returns wrong values
Date: Mon, 26 Feb 2007 16:03:43 +0100 (CET)
Created on: MaintCage
Type: bugfix
Problem Description (Customer terms)
On a non-unicode installation, the bshell function set.max and set.fmax returns values which can not be stored in the database.
Workaround
high_ascii_tolerance_mode:1 in $BSE/lib/defaults/all
Test Procedure
Pre conditions:
1. Non unicode system, ($BSE/lib/tss_mbstore6.2 contains: * )
2. high_ascii_tolerance:0 ($BSE/lib/defaults/all)
function main()
{
string str(10)
set.fmax(str) | str=~~~~~~~~~~
}
Maximum characters:
Z Unicode
~ Non Unicode and high_ascii_tolerance_mode=0
ÿ Non Unicode, ISO8859-1 and high_ascii_tolerance_mode=
Affected Executables bshell6.2
Motive source SDIS:ERP-00000-13267Also refer to -
SolutionID 227232
CreatedBy Kapteijns,Ad
CreatedOn 2008-01-31
ModifiedBy Wal,Geert van der
ModifiedOn 2008-02-06
StatusDescription Published
TypeDescription QR: Error Standard Software

Solution Description English Illegal characters removed before unicode conversion.
and,

Infor Enterprise Server 8.5
Administrator's Guide
Document code U8854G US
Release Infor Enterprise Server 8.5
Publication date November 14, 2008

High Ascii Tolerance
Important!
The following only applies to ERP LN environments that do not run in Unicode mode.
You must set the high_ascii_tolerance resource to 0 in the following situations:
If your ERP LN environment is a production environment and you plan to convert the environment to Unicode. If your ERP LN environment is a development environment and you plan to deliver software components or translations. If high_ascii_tolerance is
not set to 0, problems will occur when the delivered components are imported in Unicode environments.
To set high_ascii_tolerance to 0, add the following line in
the $BSE/lib/defaults/all file:high_ascii_tolerance:0