I was using ODBC initially. I switched to OLE DB and that solved the issue.
-Original Message-
From: Andy Ewings [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 09, 2000 11:21 AM
To: '[EMAIL PROTECTED]'
Subject: RE: upsizing access to SQL server
I've just run a small test here and had no problems. I created an Access
database with 1 table in it with a memo field with data in it.
I then used then imported data into SQL using the Import wizard in SQL 7. I
did this by selecting MS Access as the source, My SQL server as the
destination (selecting the datbase too), selected Windows NT authentication,
selected "Copy Table(s) from the source database", and it worked fine. It
brought in the field as an nText.
Is this along the lines of what you tried?
-Original Message-
From: Jeff Sarsoun [mailto:[EMAIL PROTECTED]]
Sent: 09 August 2000 16:00
To: Cf-Talk@Houseoffusion. Com (E-mail)
Subject: upsizing access to SQL server
I am running into memo field issues when upsizing to SQL server 7.0?
I
have been trying to upsize an access2000 db to SQL server by using both the
wizard interface and "import data", but keep getting the error:
"error at destination for row #1, errors encountered so far in this task:1.
Query based insertion or updating of blob values can not be supported."
I searched the cf-talk archive web site for this error and found a
couple
of entries but the fixes prescribed, such as using "import data" rather than
the upsize wizard, (which seem to be the same wizard), did not work for me.
I am selecting Microsoft Access as the source and Microsoft ODBC
driver for
MS SQL server as the destination. The default settings are using the ntext
data type by default for my Access memo fields. If I continue I get the
above error for every table that has data in a memo field in my access db.
If I change the data type to varchar or nvarchar it works, then I can change
the datatypes back to ntext with no problems.
I have two problems with this work around.
1. I have quite a few very large access databases that would require large
amounts of time to manually make these changes.
2. Data loss could occur due to limits of varchar and nvarchar data types.
If anybody has experienced this, I would appreciate some input.
Thank you
--
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=listsbody=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
--
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=listsbody=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
--
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=listsbody=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
