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.