Difference: Appx610Features (28 vs. 29)
Revision 292021-05-17 - MisaghKarimi
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
| Line: 25 to 25 | ||||||||
| The new API's have been enhanced to work with Unicode fields, but the older ones have not. You may need to update your applications to use the newer APIs. | ||||||||
| Deleted: | ||||||||
| < < | Since Unicode fields require 4 bytes per character, the maximum size of an Alpha/Text field is now 1M (1,048,576 characters). The maximum record length for an APPX/IO Type 9 (Large File) increased to 4,194,560 bytes but APPX/IO Type 1 file remains at 32K. Oracle or MS SQL Server don't have record length limit. | |||||||
Unicode is not accepted in ILF statements or Enduser/Designer Selections in a Query. Unicode is accepted in a Query at runtime. If you must refer to a Unicode character in ILF, you can use the \uxxxx syntax. For example, to use the ❤ symbol you could use:
SET --- TEMP 1 = \u2764 | ||||||||
| Line: 44 to 42 | ||||||||
Changes in Release 6.1.0Here is a list of the changes in Release 6.1.0: | ||||||||
| Added: | ||||||||
| > > | Record Length and Field Length Limits IncreasedThe maximum size of an Alpha/Text field is now 1M (1,048,576) characters. The maximum record length for an APPX/IO Type 9 (Large File) increased to 4,194,560 bytes. This is enough to store a maximum field size (1M Unicode characters) + maximum key size (255 bytes) + 1 alignment byte. APPX/IO Type 1 file record length limit remains at 32K. Oracle or MS SQL Server don't have record length limit. | |||||||
UnicodeYou can now specify a 'Unicode' encoding type for Alpha and Text fields. This is entered in the Additional Attributes dialog box: | ||||||||
| Line: 74 to 75 | ||||||||
| Both versions can be installed and operate on the same server at the same time if they are installed in to separate directories. Regardless of whether you install APPX as 32-bits, 64 bits or both, the applications you develop or upgrade from, will run on either 32 bit or 64-bit 6.1 APPX without further consideration as to bitness. | ||||||||
| Added: | ||||||||
| > > | External Databases Quick RestructurePlace holder... | |||||||
Desktop Client Uses external Text ViewerThe Desktop Client now uses an external program for viewing text report. Previously these would be displayed in the client itself. The text viewer to use is specified in the client settings: | ||||||||
| Line: 86 to 90 | ||||||||
Language TranslationLanguage Translation uses the new .UTIL COMPUTE HASH to compute hash values in the Dictionaries. Your Dictionaries are automatically converted during the migration. | ||||||||
| Added: | ||||||||
| > > | New Predefined FieldsPlace holder... | |||||||
New & Revised APIsAll the .TEXT APIs have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware that this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). | ||||||||
View topic | History: r48 < r47 < r46 < r45 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback