Bug?
GCC Consulting
gcc at optonline.net
Wed Mar 31 20:49:07 PST 2004
-----Original Message-----
From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com] On Behalf Of Courtney
Sent: Wednesday, March 31, 2004 3:43 PM
To: Filepro-List
Subject: Bug?
I found a bug in filePro (I think)
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?
I know the solution is to move the ymd field to a dummy 8,mdy/ field than that
dummy field...but I shouldn't have to...
'post fields to new record, or refresh existing record
cko(2)=nwp(4);cko(3)=rt;cko(4)=7;cko(5)=34;cko(6)=tr
field cko(4) is the 8,mdy/ field and field 7 is defined as 6,ymd
Courtney Karl Seith
North Shore Agency
------------------------------------------------
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")
Richard Kreiss
GCC Consulting
More information about the Filepro-list
mailing list