Do a replace on the VFP date fields and make the empty dates null.


>A brief background, I'm rewriting a FoxPro application as stored procedures in SQL Server 2000. ASP.net in C# is the front end. I posted the following on the SQL Server 2000 board yesterday but haven't received a response yet. I'd really appreciate any feedback anyone can provide:
>
>"I'm trying to track down the cause of a discrepency
>between my FoxPro tables & the SQL tables which were
>created using the DTS Import appl.
>
>When I try to Import into SQL using DTS I receive the
>following error: 'Error at Destination for Row number 1.
>Errors encountered so far in this task: 1. Insert error,
>column 5 ('dateadded', DBTYPE_DBTIMESTAMP), status 6:
>Data overflow. Invalid character value for cast
>specification.'
>
>When I use the FoxPro Upsizing Wizard I am able to export
>the table to SQL however the SQL tables consistently ends
>up with fewer rows than the original table (FoxPro --> 379
>records; after import into SQL there are only 343 records).
>
>Some of the FoxPro records have empty date fields, however
>I modified the T-SQL code to allow for nulls (only after I
>received the error the first time. Modifying the code
>changed nothing).
>
>The T-SQL code generated by DTS created a datatype for the
>FoxPro date fields as smalldatetime. I changed that to
>datetime but it didn't resolve anything. BTW, the FoxPro
>date data is in the format mm/dd/yyyy.
>
>Has anyone else experienced this problem or knows where I
>should begin looking for answers? Thanks."