>I'll be doggoned, you are right! I can duplicate the problem in VFP 6 SP3 for any dates in the format mm/dd/yy --- in fact, all of them with non zero years come out with 00 as the century.
>
>I guess a workaround to this would be to change the date field to a character field. Add a new field that's the true date field. After the append, do a REPLACE realdate WITH CTOD(chardate)....this seems to respect the CENTURY settings.
>
>
>
>
>>Yes -- here is my syntax:
>>
>>SET CENTURY ON
>>SET CENTURY TO 19 ROLLOVER 48 &&y2k compliance
>>
>>APPEND FROM (lcFilename) TYPE SDF
>>
>>I am looking into the rollover value -- maybe too big?
>>
>>Jill

PMFJI:

Yeah, that's we do on the 'problem' date fields in our multi-GB download imports every nite. Of course the easy ones are already coming in with 4-digit year formats, but there's always the ones coming from the lazy mainframe programmers that don't...

Rob