Very Computer

The fox table has 5 different date fields in it. There is no constraint on
these fields...it doesn't care if a value is in it or not.  It does not
allow nulls either.
The date field in fox is a DateTime, the Date Field in MSSQL is datetime,
allow null

Anyway it is a pretty straight forward deal....just copy all from fox to
sql.  About half way thru the jopb it errors out with:
Insert error, (Fieldname),DBTYPE_DBTIMESTAMP, status 6 Data Overflow
Invalid character value for cast specification

thanks

Quote:>I need a work around for this flipping error.  I am using odbc to connect to
>a foxpro freetable and copy fields to a MSSQL2000 table.

>The fox table has 5 different date fields in it. There is no constraint on
>these fields...it doesn't care if a value is in it or not.  It does not
>allow nulls either.
>The date field in fox is a DateTime, the Date Field in MSSQL is datetime,
>allow null

>Anyway it is a pretty straight forward deal....just copy all from fox to
>sql.  About half way thru the jopb it errors out with:
>Insert error, (Fieldname),DBTYPE_DBTIMESTAMP, status 6 Data Overflow
>Invalid character value for cast specification

>thanks

Simplest way to determine the bad data is to open the DataPump task, and
turn on the error log. Select the SQL 2K not SQL 7 format and output all
the info you can.
--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

This, both upper and lower is well outside of SQL Server's ranges

--

Allan Mitchell
http://www.sqldts.com