January 22, 2004 at 10:09 am
We are trying to import data from Foxpro in SQL Server 2000. We are facing some problems with doing this. We then imported this data into Access but the new problem we are facing is that the memo fields are truncated to 255 char in length from access to sql server.
Any suggestions
January 22, 2004 at 3:21 pm
Is the data type for the field in question the same throughout all your databases, as you move this data through each?
January 22, 2004 at 10:16 pm
Question #1: Is the date coming from SQL Server to FoxPro, or is it coming from FoxPro to SQL Server?
I've seen sometimes that the oledb provider will sometimes read the 1st 8 or so rows to automatically determine the datatype. Excel is a classic example of this since you can't set the datatype of the row via the provider.
If all else fails...go the lowest common denominator. Go to flat text files.
January 23, 2004 at 5:44 am
One more question: what tool are you using for importing from Access into SQL Server?
Russel Loski, MCSD
Russel Loski, MCSE Business Intelligence, Data Platform
January 23, 2004 at 6:28 am
The data is migrating from FoxPro --> SQL Server. We are using DTS for all data migrations. Using DTS for moving the data to a delimited file also truncates the data, and the suggested work around does not work...
The datatype in Foxpro and Access is memo and for SQL Server is text...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply