Re: XPA3.3 with MSSQL and collation CI #xpa
Adrian,toggle quoted messageShow quoted text
You need to implement an appropriate, case-insensitive, Alternate Collating Sequence (ACS), so Magic "thinks" the same way as your backend database in this regard. Lacking an ACS, Magic compares the ASCII values of characters to determine if they're "equal" – "A" and "a" have different ASCII codes and, so, are not "equivalent" characters. Implementing an ACS is also the way to get Magic to treat letters with and without diacritical marks, ex. "N" and "Ñ" as equal characters for sorting purposes.
To specify an ACS for ANSI columns in the Studio, select Options, Settings, Environment from the pulldown menus. Click the "External" tab and, on line 17, specify the fully-qualified name of the ACS file. Logical names are supported. Magic expects ACS files to contain exactly 265 bytes in 17 lines. For example, the following 17 lines comprise a case-insensitive ACS that exactly implements Pervasive's case-insensitive handling of ANSI data:
You need to restart the Studio in order for this change to take effect. Note that this change is GLOBAL, that is, affecting all Alpha columns and virtuals.
I do not know how to affect this for MSSQL backends nor for Unicode columns.
Steven G. Blank
On 8/18/2021 4:53 AM, Adrian Wick wrote: