Hi Jim,

  Sorry for the short delay in getting the reply for your query.

Jim wrote:

> 1)  VGETYYYYMMDD and VPUTYYYYMMDD:  These intrinsics convert dates
> to and from YYYYMMDD format.  But what field formats are supported?

  MDY, DMY and YMD.

> And how does the conversion take place?  For instance, would a MDY
> field be converted to YYYYMMDD by VGETYYYYMMDD?

  If VSETNEXTCENTURY variable is not set,

    MDY field with field length 6 would produce   MMDDYY<blank><blank>
    DMY                                           DDMMYY<blank><blank>
    YMD                                           <blank><blank>YYMMDD

    MDY field with field length 8 (4-digit years) MMDDYYYY
    DMY                                           DDMMYYYY
    YMD                                           YYYYMMDD

  If VSETNEXTCENTURY variable is set,

    MDY field with field length 6 would produce   MMDDYYYY
    DMY                                           DDMMYYYY
    YMD                                           YYYYMMDD

   [Here the conversion from 2-digit years to 4-digit years is
    by the logic:
     00..49 => 2000..2049 ; 50..99 => 1950..1999]


>  How about a CHAR
> or NUM or DIG field with valid data in it? What about validation
> (month in range 01-12, day in valid range for month)?

   Same as the way it is handled in VPUTYYMMDD and VGETYYMMDD.

Two new intrinsics have been added to VPLUS to handle dates in the next
century. These intrinsics are similar in structure and function to the
existing intrinsics VGETYYMMDD and VPUTYYMMDD respectively. The difference
is that the date values handled by the new intrinsics contain 4-digit
year components.

> 2)  What is the point of having a VPUTSAVEFIELD intrinsic if it does
> not modify the value of the save field?

Two new intrinsics have been added to VPLUS to enable applications to
access Save Fields. The values of Save Fields can be accessed/changed
using the new intrinsics.

   VGETSAVEFIELD   - Copies contents of the specified save field from
                     save field buffer *in memory to an application*.

   VPUTSAVEFIELD   - Copies data from an application to the specified
                     save field *in memory*.

   However, these intrinsics cannot/do not  modify the values of
   save fields in forms file.
               ^^^^^^^^^^^^^

Hope this helps,

Gopi ([log in to unmask])
CSY R&D India, Bangalore.

____________________________________________________________________________
From: Jim Phillips <[log in to unmask]>
Subject:      VPLUS & MPE/iX Express 2
To: [log in to unmask]

Can someone help me in understanding these "enhancements" to VPlus:

1)  VGETYYYYMMDD and VPUTYYYYMMDD:  These intrinsics convert dates
to and from YYYYMMDD format.  But what field formats are supported?
And how does the conversion take place?  For instance, would a MDY
field be converted to YYYYMMDD by VGETYYYYMMDD?  How about a CHAR
or NUM or DIG field with valid data in it?  What about validation
(month in range 01-12, day in valid range for month)?

2)  What is the point of having a VPUTSAVEFIELD intrinsic if it does
not modify the value of the save field?

Thanks for any help or insights you can provide.

Jim Phillips
___________________________________________________________________________