Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-03-25 : 07:43:04
|
| Tim writes "I'm trying to transform foxpro tables to a sql server database. Any wizard I use (Import/Export in sql server, SQL Server Upsizing Wizard in foxpro) works great with the exception of translating foxpro columns with a "memo" data type. The documentation claims that the foxpro wizard can export to Sql Server, no sweat. Just isn't true. I can find a common source by using ADO (it reads both), and by making a component that reads the foxpro and updates the SQL Server. BUT, I'm wondering if there is any hope of SQL Server being able to handle this with out me building another component for the application. Any suggestions? Probably out of luck because of the foxpro..... Throw me a bone here." |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-03-25 : 12:49:39
|
| Do you get an error when translating the memo data type? Have you tried creating the base schema in SQL Server then just transferring the data? If you create the base schema, you would probably specify the text data type for the memo data type. By doing it this way, SQL Server just has to convert the data.Tara |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-03-25 : 20:29:31
|
| This might be related to the driver being used to import the data. I recently migrated a Clipper/Foxpro format data file containing a memo field to SQL Server and it worked flawlessly. If you're talking about the wizards in Visual Studio 6, you'll probably have to update the MDAC components if you're migrating to SQL Server 2000. You can get the latest here:http://www.microsoft.com/data/download.htmYou might just try using the Import/Export wizard from SQL Server, instead of the Visual Studio Wizards, and see if they're more successful. |
|
|
|
|
|
|
Data transformation