Hi Christof,

Right. But that would be in a broad band Y2K scenario, but CTOD will still work within set century and roll over.

Or am I still missing something?

Thanks for caring and kind regards,

Marc


>Hi Marc,
>
>>This advise is not linked to the Y2K problem, is it?
>
>Well, in a way it is. Every ambigiuos date constant in your code might cause problems sooner or later. For example, CTOD("01/02/10") could mean a lot. It might be the first of February, or the second of January depending on the SET DATE setting. It might be 1910 or 2010 depending on the SET CENTURY setting. With DATE(2010,1,2) you don't have these problems. It's definitely the second of January, no matter what the settings are.
>
>Christof