>Nadya
>
>This all looks like a bug to me. At least, I could not find it somewhere clearly documented in VFP 7/8/9. Here is how to reproduce the behavior:
>
>

>CLEAR
>
>set century TO 19 ROLLOVER 55   && default
>
>?SET("century",2)  &&55
>
>lnyear=VAL(RIGHT(DTOC(DATE()),2))+1
>set century ON TO 19 ROLLOVER lnyear
>
>?SET("century",2)   *&& still 55, why?
>
>for i=1 to 10
>	?ctod('01/01/'+ transform(m.i))  && rollover 6 does not work
>NEXT
>
>set CENTURY TO 19 ROLLOVER lnyear
>
>?SET("century",2)   && now it is 6, because of ON was removed?
>for i=1 to 10
>	?ctod('01/01/'+ transform(m.i))   && rollover 6 works
>NEXT
>
>* Try with ON again
>set CENTURY ON TO 19 ROLLOVER lnyear
>
>?SET("century",2)     && it is 6 however, why?
>for i=1 to 10
>        ?ctod('01/01/'+ transform(m.i))  && rollover 6 works, and with ON !?
>NEXT
>

>
Let me check exactly how this command coded in our framework, because I set nCentury properties and nRollover to the correct values and the class still gives me an error when I type 1/1/43.