Migrating Foxpro table with memo fields to SQL Server

Hi Everyone,
Here is the issue : Getting error while transferring
foxpro data with memo fields. If I omit memo field, its
fine.
Could anyone know, how can I overcome this issue ?
Thanks in advance,
SKHow are you importing the data? Which version of FoxPro? What's the error
message?
The Visual FoxPro ODBC Driver supports memo fields (upto at least Fox 6.0)
and the DTS Import Wizard will automatically import them as Text columns if
you let it create the table for you. Fox 7.0 and 8.0 come with the newer
OLEDB driver. I haven't tried it with memo fields in DTS but I would expect
it to support Memo since the older driver does.
--
David Portas
--
Please reply only to the newsgroup
--

Migrating data into dbf file

I have to migrate datat from my table to my accounting system.

The table fields of the accounting system are different from my sql table and the Acc sys accepts only .DBF files.

I would have to migrate the data daily.
So my question is: whats the best approach for doing this work.
Should I create a nother table in Sql Server with the field names as the dbf file and write a SP to get all the data from another tabel into this one and then using export wizard to export data into a dbf file.
Or is there any better appraoch
regards

Hi,
Perhaps the better approach is a Data Trasformation Service scheduled daily.
Best regards

migrating (cloning?) DTS mapping

I have a DTS package on SQL Server 2000 that loads a table from a text file daily. The text file has 148 distinct fields that are mapped to a corresponding 148 columns on the table. I need to recreate the package to SQL Server 2005. Is there any shortcut to replicating the mapping from DTS to SSIS or do I need to redo from the beginning?

Dennis Cronin wrote:

I have a DTS package on SQL Server 2000 that loads a table from a text file daily. The text file has 148 distinct fields that are mapped to a corresponding 148 columns on the table. I need to recreate the package to SQL Server 2005. Is there any shortcut to replicating the mapping from DTS to SSIS or do I need to redo from the beginning?

If there are 148 columns in both source and destination then you can probably use the Import Wizard to build the package for you and then adapt it as you wish. very easy and very quick.

-Jamie