Problem:
--------

I am upgrading to version 4010 on my outgoing documents.  How does the 
EDI module handle ‘date returned’ values on a date?  Note that my MXP 
dates may or may not be Y2K compliant in database storage.

Solution:
--------

Internally, the length of the date value for versions 4010 and up are 
longer than those in previous versions. Thus our EDI module takes the 
length into consideration and assigns the century to the date.

For those of you who are more technically inclined, here is 
an explanation of how the program works:
------------------------------------------------------------

This is what is happening in the code:

The EDI module has a field on the edi-segment and edi-seg-over records 
called ‘max-length’ that is set to value 8 for versions 4010 and up, and 
to value 6 for earlier versions.  This ‘max-length’ value is pre-defined 
in the base records that you load into your system when your EDI setup 
person loads in your base/virgin maps.

If the value within ‘max-length’ of the out-going date position is 6 
then the 2-digit century prefix does not appear in the outgoing date 
otherwise, if it is 8, the 2-digit century prefix appears in the 
outgoing date.