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

None of my business. My business is the system.

Okay, now the honest answer: Some I would warn that that doing something like that could be very dangerous. Others, I would encourage it.

>
>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.

The system that they work on is just about all they work on. They won't see any other systems that have dates. So the standard means nothing to them. And does entering a date field in 99/99/99 format and later re-entering that field and seeing the format 9999/99/99 make any sense? Are we just making excuses for this flaw?

>
>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).

ROLLOVER is being used. That is the main reason for going to 5.0. If you enter a 2 digit year for a date Jan. 1, 2000 or later and go back to the field (tab to it, for instance), the field display a 4 digit date. If you do the same for a date earlier than Jan. 1, 2000, it only displays 2 digits upon re-entry. This is inconsistent behaviour. If you know how to fix this, ***please*** let me know how.

>
>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.

I report to the President of the company. I don't report to the users. Users are not overstepping their bounds. They have been asked a question regarding their preference. They have answered the question.

Joe