>might be odbc drivers -- running empty dates to crystal reports show as 12/31/1899. useful, don't you think?

In my application, if the user leaves the birthdate empty, VFP was saving 01/01/1900, making the person 97 years old! I was able to fix any new records added by adding a default of NULL to the SQL Server table. I finally got all the bad data fixed by running a replace program.

If the problem was in the ODBC drivers, I think MS Query would have the same problem.

Jeff