Got confused because a table was comparing it to always had its' date in 01/01/2006 - regardless of the SET CENTURY. Looked a bit further and the date was really a character.

Guess I need to understand how to make VFP date field dbase compatiable.


>>I have a .dbf free table that has dates as 01/01/06. This seems to be causing a "database engine failue" when I use this dbf as my data source in a Word Mail Merge. (I selected dbase files). I know the fix is to SET CENTURY ON in the code before creating the .dbf. But how do I converted my 01/01/06 to 01/01/2006 in my existing .dbf?
>>
>>Brenda
>
>Data was kept with full century info, so you don't need to convert it. Just check it to see if the year is not 1906 :-)
>

>SET CENTURY ON
>USE MyTableWith06DateField
>BROWSE NORMAL
>