Hi Mike,

I'm not sure if it's a bug or behavior change between VFP6 and VFP7. When date format is set to SHORT or LONG, the dates before {^1601-01-01} evaluate to the empty value in VFP6 and generate an error in VFP7.

* Each line below returns empty values in VFP6 and  
* generates an error in VFP7 and later.
SET DATE TO SHORT
? ctod("01/01/1600")	
? dtoc({^1600-01-01})

When you type the third digit in the year (200), you get value '10/31/200' which is less than {^1601-01-01}. In VFP6 conversion to date returns an empty value, in VFP7 result is undetermined.

>I now know why you're not seeing the same behavior. Our environment is set up to use system settings. Under Tools->Options->Regional. If that's not set, the behavior is different.