Thanks for that Jim.
The sad bit is that if you're converting a 2.6 app just because you want Y2K you've got to rewrite the screens anyway. Dang!
So, in effect 'set century off' doesn't work anymore. I've noticed grids/browses are strange too.
I think I'll just go with the flow and force the users to enter the extra two digits.

>David,
>
>Despite the following excerpt from "The Hacker's Guide to Visual FoxPro 6.0" by Granor and Roche (Hentzenwerke Publishing). . .
>The ROLLOVER portion allows you to split up the dates, so that those on or after a certain year fall in the century specified, and those less are assumed to be in the next century. In many cases, these two settings can alleviate the need to require four-digit dates. ,
>it appears that even VFP 6 insists on showing the century portion. I would guess that it is the usage of "ROLLOVER" which triggers this.
>
>By the way, I believe that this is the 'accepted' way to handle dates generally in products like VFP.
>
>I guess you'll have to use a TextBox and do internal conversions as required.
>
>Good luck,
>
>Jim N
>
>>In VFP5 if ...
>>SET CENTURY OFF
>>SET CENTURY 20 ROLLOVER 60
>>and I create a date text box on a form with a value of {}, then enter a date of say 12/12/89, it displays just that. If I enter a date of
>>12/12/12 the display changes to 12/12/2012 with the last '12' partly hidden.
>>If I use VFP6 it's more consistent, but the full century always shows, despite it being turned off.
>>
>>What gives? Can I make it work to only accept and display the 2 digits?