Joe,

What would you do/say if your users "decided" that they prefer to drive on the other side of the road from everyone else??

Don't say this isn't the same thing, because it *is* - a 'global' standard has been set which, summarized (and no, I cannot point you to the "official" document) says that to prevent any possible ambiguity, all dates shall always be shown with 4-digits.

Now that doesn't prevent you from letting your users enter 2 digits - *you* have to program for it. And VFP 5 has SET...ROLLOVER to help you with that.
As for MS 'fixing' it in VFP 5, well they would have had much more reason to fix FPD/FPW 2.6, but they elected not to, so 5.x, likely will see no change (not to mention the STANDARD above).

Sometimes users overstep their bounds. Looks like this may have been such a time. I notice you are in insurance services - a business particularly sensitive to dates.

Good luck,

Jim N

>Thanks for your input, but I design systems to the users' specs. This has been discussed and they have decided that they want 2 digits.
>
>Reports always show 4 digits. Data entry forms always show 2 digits. This is the standard that we have set.
>
>How is the ROLLOVER clause useful if you are showing 4 digits anyways?
>
>IMHO, this is an issue that should have be fixed. Is this a (MS) way to force a switch to VFP 6.0?
>
>Take care,
>Joe
>
>
>>>VFP 5.0b.
>>>SET CENTURY To 19 ROLLOVER 5
>>>
>>>When a date is in the 20th century, say Dec. 21, 1999, it looks like this is a TextBox with Format property="D": 99/12/21
>>>
>>>This is good.
>>>
>>>When a date is in the 21st century, say Dec. 21, 2000, it looks like this is a TextBox with the Format property="D": 2000/12/21
>>>
>>>This is not good.
>>>
>>>Is there a way around this? I want to see two digits for the year whether 19xx or 20xx.
>>
>>Joseph,
>>
>>Seriously consider always displaying the full year (all four digits) as anything else is ambiguous to the user.