dbTalk Databases Forums  

Translation issue

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Translation issue in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
robert britton
 
Posts: n/a

Default Translation issue - 09-15-2003 , 12:36 PM






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!

Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Translation issue - 09-16-2003 , 02:00 AM






You could have a look at inserting the Foxpro Date Time fields into this
function and inserting.

Formatting Character Data into Datetime fields
(http://www.sqldts.com/default.aspx?249)

--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"robert britton" <bbritton (AT) mackenzie-childs (DOT) com> wrote

Quote:
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!



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.