| |
| META TOPICPARENT |
name="Main.Appx600Installation" |
APPX 6.1 Upgrade Instructions |
| |
5. APPX now uses a LF character (ASCII 10) instead of a ¶ (ASCII 182) as a line feed character in text fields. Existing text data will display the ¶ character instead of a new line. To correct this, you need to search any text fields for a ¶ and replace it with a LF character. If you were already using APPX_END_PARAGRAPH to set the line feed to 0x10, this is no longer necessary as your data is already using a LF. |
|
<
< | 6. Field Type of fields that are storing pointer values have been changed from Numeric (binary) to Alphanumeric. If you use appx-32bit, they are now ALPHA(4), and ALPHA(8) if you are using appx-64bit. Most of these fields are used internally and you shouldn't worry about them if you have not used them in your application. Here are the list of pointer fields in APPX: |
>
> | 6. Field Type of fields that are storing pointer values have been changed from Numeric (binary) to ALPHA(8). Most of these fields are used internally and you shouldn't worry about them if you have not used them in your application. Here are the list of pointer fields in APPX: |
| |
- 0AD IMGEDIT INT ADDR
- 0AD SEGEN SE POINTER
|
| |
- 0LA STACK PCB POINTER
- 0LA STREAM FILE POINTER
- 0LA STREAMS FILE POINTER
|
|
<
< | 7. RETURN CODE is still 4 byte binary field. So, you cannot expect to receive an 8 byte pointer (in 64-bit release) in the return code field. |
>
> | 7. 0LA RETURN CODE is still a 4 byte binary field. So, you cannot expect to receive an 8 byte pointer (in 64-bit release) in the return code field. |
| |
8. Regular Expression library has changed to support Unicode characters. The new library doesn't like blank or unescaped patterns. You will get a run-time error if it doesn't like the pattern. |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.