date problem

[George Simon]

To me, that sounds like a date field that used to be 8,mdy/ now is 10,mdyy/
and that something is trying to gram the year by doing a mid(dt,"6","2") and
instead of getting the year it is now getting the century.  But that is just
a guess.

----- Original Message -----
From: "GCC Consulting" <gcc at optonline.net>
To: "Filepro 2 List" <filepro-list at lists.celestial.com>
Sent: Wednesday, August 11, 2004 6:42 PM
Subject: OT: date problem


>
> Let me first say this IS NOT A FILEPRO PROBLEM.
>
> My client uses edi to send his daily invoice schedule to his factor.  This
just
> lists the invoice date - mdyy/, invoice #, customer, and invoice amount.
>
> I generate an ASCII file which is processed by a dBase program(yea, I
know, the
> enemy) which creates the VICS edi format required. They have been doing
this for
> over 3 years without a problem.
>
> Do to an incorrect invoice date. They called the factor and advised them
that
> the date would need to be changed and the schedule resent.  At this point,
they
> were advised that the invoice date transmitted was 20200810.  That's right
2020.
>
> We corrected the date to 08/11/2004, regenerated the transmission.  Again
we
> were advised that the year was 2020.
>
> I examined the dbf file used to create the edi file and the date there was
> 8/11/2004. The programmer who handles the EDI portion had already left his
> office so I couldn't check the last piece of the puzzle, his translation
> program.
>
> As this has worked for more then 3 years, can anyone think of a reason
that the
> program would cause this type of problem?  Monday's transmission was OK.
>
> Richard Kreiss
> GCC Consulting
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list