<div>
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?
</div>


<div>
Looks like you could be a victim of this: see MS KB article 259893<br />
<br />
SYMPTOMS<br />
When you apply formatting, such as a closing or opening angle bracket (&gt; or &lt;), to a field with the Memo data type, the data in the field appears truncated after the 255th character. <br />
CAUSE<br />
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. <br />
<br />
You should probably see MS KB arrticle 194975:<br />
SUMMARY<br />
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. <br />
MORE INFORMATION<br />
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.<br />
**************************<wbr />**********<wbr />*********<br />
Good luck.<br />
<br />
-- Eric
</div>


<div>
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.<br />
<br />
Thanks for the help<br />
<br />
James
</div>


<div>
No comment has been added lately, so it's time to clean up this TA.<br />
I will leave the following recommendation for this question in the Cleanup topic area:<br />
<br />
PAQ with points refunded<br />
<br />
Please leave any comments here within the next seven days.<br />
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!<br />
<br />
stevbe<br />
EE Cleanup Volunteer
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
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.<br />
<br />
It's quite important that I get this fixed quickly<br />
<br />
Any ideas on how to get the whole entry into the recordset?<br />

</div>
</div>


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?


truncation of memo field to 255 characters when creating a recordset

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.