If I SET CENTURY TO 20, it will know. I just don't know if that command is available in 2.6.

I have the link to his article.

Thanks,

Michelle

>Michelle,
>
>I don't know. It is in FPD2.6 and FPW2.6. How will your system know that 00 is 2000 since CENTURY ON defaults to 20th century for 2-digit years.
>
>You will need to write your own CTOD or use Christof's function. (Do you have it?)
>
>
>>If it knows 00 is 2000, it shouldn't have a problem. What version did SET CENTURY TO start in?
>>
>>Thanks,
>>
>>Michelle
>>
>>
>>
>>>Michelle,
>>>
>>>You will need something for February 29, 2000 since CTOD("02/29/00") will give an error.
>>>
>>>Something like:
>>>
>>>

>>>IIF(CharacterDateField = "02/29/00", ;
>>>    CTOD("02/29/2000"), CTOD(CharacterDateField))
>>>

>>>
>>>>>
>>>>>>I am trying to make an old 2.6 app Y2K compliant. What I would like to do is have it recognize 00 and up as 2000+, but not put the century in. They have character based dates, and I'm afraid if it sticks the century in that it won't work. Is this possible?
>>>>
>>>>They're 2 digit years and I'd like to keep them that way. Ambiguity is not a problem. All dates are either the current year or the previous year. All I really need is to have CTOD("01/01/00") (gr than sign) CTOD("12/31/99") be true.
>>>>
>>>>Thanks,
>>>>
>>>>Michelle