>>That's strange. Shure you do not anything else with SET CENTURY on startup? Because 19 50 means the 50 needs to be set somehow.
>>What happend if you create a numb private form and put into init event:
>>

>>?SET("Century"),SET("Century",1),SET("Century",2)
>>SET CENTURY TO
>>?SET("Century"),SET("Century",1),SET("Century",2)
>>

>>and run the form?
>>because that is what should be default.
>>
>>BTW, Hilmar seems to have twitted me. Possibly you can hint him that all the stuff when SET CENTURY switches to what century and rollover is within HELP SET CENTURY? It's a bit awkward written, but by simply running some test one can figure it out.
>>
>
>OK, thanks for the information. (Anyway, I still find the VFP behavior weird...)

I have no trace about its use bevore the Y2K stuff was introduced, but this could be to keep programs that simple have used SET CENTURY TO 19 stable in 2000+ They will not fail until 2050, even if it is a bad solution