Christof,

RE:'ve seen this on many occasions. Basically, this happens every time VFP converts the date value into a different type. This can happen on index operations, too. Have you checked the content of the table? ...when you change it to something else, you can enter any date. You might have data in the table that has been entered incorrectly a long time ago.

I tried entering 1/1/1600 on the old version of the program before this update of VFP9SP1 and SET SYSFORMATS ON and it let me enter that date - I'll work on seeing if this simulates the error. If so then I know how to detect it and fix it before the error occurs. Thanks for the information!

From: Ed