>I'm trying to move a few Foxpro for Windows Tables to a SQL Database (destination table exists) and I'm running into a few issues with the datetime fields on the SQL side. Is there a way in Foxpro to adjust the source table's date fields to eliminate multiple additional passes on the destination table to correct datetime fields. What happens is a empty datefield is defaulting to 12:00 am January 1st 1899 on the SQL side.
>
>thanks,
>
>Don

Don,
SQL server datetime fields cannot have empty values but .null. Set your table on SQL server to accept null for datetime fields and either send them as null or do not send at all.
Cetin