>Hi James,
>
>I'm not sure, but it looks likes you're making an incorrect assumption here. In the first example, you say that if the user has a bond that matures on 1/1/2109 and they would be likely to enter 01/01/19. Why? Further, the SET CENTURY...ROLLOVER correctly interprets that entry as 01/01/2019.
>
>To enforce entry of non-ambiguous dates, VFP 6.0 has SET STRICTDATE as well as a StrictDateEntry property to control this.

And if you are using 5.0, try creating a subclassed textbox for dates in which you can force the user to type in all 8 digits for a date. I've had to do this. The Y2K requirement was for typing all 8 digits which forces the user to type in the 4 digit year. The control uses an internal counter which is incremented in the .Keypress event. Any change to the date blanks the whole field forcing the user to once again enter 8 digits.

Although I have 6.0, I haven't checked out the date entry in it yet.

Steve