![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Ok. I have a simple situation. I have a single Foxpro table which I've created an ODBC connection to using the FOxpro driver donwloadable from microsoft support. I have an OleDB connection to SQL 2000. I have created a DTS package with three elements, two connections (one to my fox pro table, one to the sql table), and a transformation task. I used DTS to create a table in my SQL database that corresponds to the Foxpro fields/datatypes of my fox pro table. My DTS task is to copy / move all the data from the fox pro table into the SQL 2000 database table. When I run the package, it screams at me because two of the datetime fields in the fox pro table have data it's not expecting. From what I can see, the fox pro source table has two datetime fields that either contain a date in the format of m/d/yyyy or the timestamp of 12:00:00 AM. I am not a DTS expert. I've used it in the past to move data back and forth between servers and databases. I've never done it from FoxPro before. Apparently, MS SQL server doesn't like the way the datetime is coming in from the foxpro table. Can someone help me by recommending how I can fix this? Thank you! |
![]() |
| Thread Tools | |
| Display Modes | |
| |