HP 3000 Manuals HP 3000 Manuals
FIELD EDITS NATIVE-3000 must be used to specify date and numeric fields within FORMSPEC. When the forms file is executed, VPLUS/V will convert the value to be consistent with the native language selected. Single value comparisons (GT,GE,LT,LE,EQ,NE), as well as table and range checks (IN, NIN), specified within FORMSPEC may contain any character in the 8 bit extended character set consistent with the selected native language ID number. When the form is executed at run-time, the collating table for the native language specified is used to check whether the field is within a range. Date Handling VPLUS/V supports several date formats and three date orders: MDY, DMY,YMD. Any format is acceptable as input when the form is executed, provided that the field length can accommodate the format. The forms designer specifies the order of each date-type field. With NLS, the alphabetic month names are edited and converted to numeric destinations using the month names corresponding to the native language of the forms file. The format and the date order are not related to the native language of the forms file. Numeric Data Decimal and thousands indicators are native language-dependent in the NUM[n] and IMPn fields. When data is moved between fields and automatic formatting occurs for data entered in any field, recognition, removal or insertion of these decimal and thousands indicators is native language-dependent. The optional decimal symbol in constants is also native language-dependent.
NOTE VPLUS/V edit processing specifications and terminal edit processing statements are separate and are not checked for compatibility. There will be no check to see that the forms designer has specified a terminal local edit (DEC_TYPE_EUR, DEC_TYPE_US) in the configuration phase which is consistent with the native language-dependent decimal indicator for the native language specified in the forms file.
Native Language Characters If a native language ID number has been specified in the forms file, the UPSHIFT formatting statement uses native language upshift tables. Range checks and the single value comparisons GT, GE, LT and LE involve collating sequences. When the form is executed, the native language collating sequence table designated by the native language ID number is used to check whether the field passes the edit. NLS features in VPLUS/V do not include support for pattern matching with native characters. MATCH uses USASCII specifications.