Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Century
- Thread starter liliana
- Start date
This is a known Y2K issue with FPW26.
Robert Bradley
Robert Bradley
Not only is this known, but even VFP 3 and 5 do the same thing and MS isn't planning on fixing them either.
This is basically due to the fact that the .DBF header where the last accessed date is kept, only has two characters to store the year. So without changing the .DBF structure (and making most every .DBF incompatible), it can't be "fixed".
Note: VFP 6, makes the assumption that if it's value is 00-79 (if memory serves) then it must be 20xx, so in ~78 years we'll have another "bad design" problem of major proportions <g>.
Rick
This is basically due to the fact that the .DBF header where the last accessed date is kept, only has two characters to store the year. So without changing the .DBF structure (and making most every .DBF incompatible), it can't be "fixed".
Note: VFP 6, makes the assumption that if it's value is 00-79 (if memory serves) then it must be 20xx, so in ~78 years we'll have another "bad design" problem of major proportions <g>.
Rick
I have used Foxpro 2.6a for years to do mail merges with MS Word for direct mail advertising purposes. I use Foxpro to access data that I purchase from a State Government Agency. This data contains dates and we query the information in the database by date. We then time our mailings based on the date ranges. We simply produce mailing labels and mail out pre-printed flyers. Foxpro has worked perfectly for our needs until these dates rolled over into the year 2000. Now the program will not find any information regarding dates later than 12/31/99. The database information is in .dbf format and comes to us on CD-ROM.
Is there any way around this problem other than using a different program. I do not like Microsoft Access.
Thanks for any assistance of any kind.
Mike
Is there any way around this problem other than using a different program. I do not like Microsoft Access.
Thanks for any assistance of any kind.
Mike
Can you make a small import program that intercepts the dbf from the CD-ROM?
In this program create a dbf the same structure as the one on CD-ROM except for a extra date field on the end.
Rename the date field in question to tempdate
name the new field at the end to the name the other date field was
use temp.dbf
set century off
append from CD-ROM.dbf
set century on
replace all OrgfieldName with tempdate
copy fields (list all but the tempdate) to whereever the CD-ROM dbf was suppose to go in the first place
David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644
In this program create a dbf the same structure as the one on CD-ROM except for a extra date field on the end.
Rename the date field in question to tempdate
name the new field at the end to the name the other date field was
use temp.dbf
set century off
append from CD-ROM.dbf
set century on
replace all OrgfieldName with tempdate
copy fields (list all but the tempdate) to whereever the CD-ROM dbf was suppose to go in the first place
David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644
infinitelo
Programmer
- Mar 7, 2001
- 319
will the query work on 2000-2001 dates without any 1999 dates?
- Status