I think you are over simplifying this issue.

You claim whoever programmed Foxpro screwed up. But if your program was written with 2 digit century, you would still have to go back and revisit so that prior dates could be entered.

Do you mean to say that if the program just grabbed the system century and you had a Invoice data file query and the user entered the dates as {12/1/99} to {1/31/00} it wouldn't error.

It sounds to me like you expect the designer of Fox or any other tool to code the logic of deciding on dates for you. As with any programming language, its a tool with that you can design with as you wish.

PF

>MS was sued just over this. The girl that sued them was correct.
>MS FoxPro programmers hosed up here, they certainly have a hard coded
>century setup instead of getting the century from the system. They should
>have lost that lawsuit but the judge declared it worked as documented.
>I know because I had to write a function that did just that - and I easily
>got the century from the current system date - foxpro has the ability to
>get it - the MS programmer just had no vision.