Convert Access memo datatype to SQL Server text type

Convert Access memo datatype to SQL Server text type

Post by Ong Boon We » Sat, 31 Jan 1998 04:00:00



        I have some data that is stored as memo in Access file. Currently, I am
using ADO to store the data from Access to SQL Server as text datatype.
However, I encountered the following message while doing so:
run-time error '-2147467259 (80004005)':

Query Based Insertion or Updating of BLOB values can not be supported.

Any help?

--
Boon Wee


 
 
 

Convert Access memo datatype to SQL Server text type

Post by Jamie Beidlema » Mon, 02 Feb 1998 04:00:00


I had luck writing to text data type columns by using stored procedures. I
then let ADO build the command parameters (including the text) then the
stored procedure handled the insert. I was using ADO in ASP.

Good Luck
Jamie


> I have some data that is stored as memo in Access file. Currently, I am
>using ADO to store the data from Access to SQL Server as text datatype.
>However, I encountered the following message while doing so:
>run-time error '-2147467259 (80004005)':

>Query Based Insertion or Updating of BLOB values can not be supported.

>Any help?

>--
>Boon Wee




 
 
 

1. Converting VFP memo fields to SQL Server text fields

Our VFP application makes rather liberal use of memo fields. For example,
we have an objects table with 25 memo fields in it. We're now attempting
to upsize this application to SQL Server. I see that there are two
datatypes for handling character strings in SQL Server that might be
useful:

1. varchar -- for text strings up to 255 characters

2. text -- for handling variable length text strings; a mimimum of 2K is
allocated for each string

It would appear that the text datatype is the best for our application
because the length of the text strings entered is highly variable. But the
prospect of having records that are a minimum of 50K (25 fields * 2K)
looks like real bad news.

I've been thinking about creating a single text field and placing all the
character string contents in it. In other words, I'd concatenate all the
memo fields' contents together and place them after an index/jump table of
some sort. Before I go to this extreme, though, I was wondering if anyone
here had any other better ideas. Is there some sort of technique that I'm
overlooking?

Geoff LeBlond
Re:discovery Software

2. LSF V2.0 Load Sharing and Distributed Batch Software for UNIX Networks??

3. convert image datatype to text datatype

4. Comparison shopping.....

5. SQL Server equivalent to Access Memo data type

6. Connect to SQL without using DSNs?

7. convert CHAR type to TEXT type (BLOB) and insert in table

8. MSJRO.DLL

9. Visual FoxPro Memo type fields into a SQL 7.0 text

10. Access Yes/No datatypes to Bit datatypes in SQL Server

11. Data Transfer from Long data type to SQL Server Text data type column

12. Datatype Memo to Sql Server