truncation of memo field to 255 characters when creating a recordset

Hi,
I am creating a recordset to be used in a website. The Website is emulating the functionality of a programmme already written in VB. One of the fields in the record set is of datatype memo, but when the record set is created all enties above 255 charaters are truncated to 255 characters, this was verified using the ActualSize function on the field. The DefinedSize of the field in the recordset is that of the memo datatype. This didn't happen in the original VB programme and it seems strange that the recordset picked up the max field size but only filled it to 255 characters.

It's quite important that I get this fixed quickly

Any ideas on how to get the whole entry into the recordset?
jbr26Asked:
Who is Participating?
 
SpazMODicConnect With a Mentor Commented:
PAQed, with points refunded (250)

SpazMODic
EE Moderator
0
 
jbr26Author Commented:
I just fond out that the truncation doesn't work when I use the UNION command in the SQL statement. Is there anyway that I could use this command and for the field not to be truncated?
0
 
ericmcaCommented:
Looks like you could be a victim of this: see MS KB article 259893

SYMPTOMS
When you apply formatting, such as a closing or opening angle bracket (> or <), to a field with the Memo data type, the data in the field appears truncated after the 255th character.
CAUSE
When you apply formatting to a Memo field, the formatting is treated as a Text field, which has a 255-character limit. The data is not physically truncated, but only 255 characters are viewable.

You should probably see MS KB arrticle 194975:
SUMMARY
This article describes how to read and write Binary Large Objects (BLOBs) using GetChunk and AppendChunk methods against fields in ADO. It also includes sample code using the NWIND sample database.
MORE INFORMATION
The GetChunk and AppendChunk methods work with the LongVarChar, LongVarWChar, and LongVarBinary column types, also known as TEXT, NTEXT, and IMAGE columns, in Microsoft SQL Server, and as MEMO and OLE fields in Microsoft Jet databases.
*********************************************
Good luck.

-- Eric
0
 
jbr26Author Commented:
I found the solution as soon as I worked out it was to do with the UNION function, which truncates memo fields to 255 characters. I used UNION ALL instead and it all worked fine.

Thanks for the help

James
0
 
stevbeCommented:
No comment has been added lately, so it's time to clean up this TA.
I will leave the following recommendation for this question in the Cleanup topic area:

PAQ with points refunded

Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

stevbe
EE Cleanup Volunteer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.