Bug?

[Jay R. Ashworth]

On Wed, Mar 31, 2004 at 11:49:07PM -0500, GCC Consulting wrote:
> I am writing a field from 6,ymd format to 8,mdy/ format...the date is 040329 and
> comes out as 04/03/29...while the year COULD be 1929, should filePro convert it?
> Courtney Karl Seith
> ------------------------------------------------
> If I am reading the date correctly, it translates to March 29, 2004.
> 
> If this is the case, the 8,mdy/ is reading the date correctly at posted, April
> 3, 2029.
> 
> This is not a bug, fp expects the values to be in the proper sequence.
> 
> You need to use a mid statement to translate the values into the proper sequence
> 
> Cko(4)=mid(7,"3","4"){mid(7,"1","2") 

That's not *MY* understanding of how system date edit fields work,
dude.

Assignments between date edit fields of different types are supposed to
Just Work, swapping elements as necessary, and consulting PFCMARK
(presumably) to fill in extra digits if going from a y to a yy edit.

Such has always been my experience, and I have utilized YYMD fields on
occasion as copies of "human readable" dates, for doing things like
multiple-field edits with descending date before fP knew how (convert
to YYMD, then subtract from 99999999, and index.  Forget whether I
stole that from Jeff or Ron... :-).  All *I* ever remember having to do
was assign.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 647 1274

        "They had engineers in my day, too."  -- Perry Vance Nelson