Importing FoxPro 2.6 for Dos into SQL Server 2000 using DTS.

Hi,
Will it be possible to imort FoxPro 2.6 for Dos into SQL Server 2000 using DTS without any issues? Will existing drivers in SQL for FoxPro work or will I need something more?
Any help will be greatly appreciated!
LizadieselAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

CarlWarnerCommented:
Since you're going from SQL Server to a FoxPro table (.dbf), you should have no real issues grabbing that data with existing drivers.  The later (latest) drivers support that older .dbf format.  Of course, I'm not entirely sure to what existing driver you're referring. If you make the assumption that a dBASE driver will work, well, it might and it might not.  Depending on what type of data is in the FoxPro table, the dBASE driver may not always work because the format could be different enough to make the driver throw errors.

If you have a Visual FoxPro driver handy, you should have no issues whatsoever (as long as the data isn't corrupt).

Visual FoxPro ODBC Driver
http://msdn.microsoft.com/vfoxpro/downloads/updates/odbc/default.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
chanitoCommented:
The issue I've seen with FoxPro and DTS is you need to define a data source in the control panel or administrative tools (DSN) for it to work.  Since it's FP 2.6 you need to define it as a free table directory.

If you use the generic Visual FoxPro Tables DSN it won't work.

I think the other issue I've come across is SQL Server doesn't like empty date fields.  If you have date fields make sure you put a value.  You can always script it later in a data driven query step to replace 1/1/1900 with a null value or something.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Databases

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.