truncation of memo field to 255 characters when creating a recordset

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?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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?
Looks like you could be a victim of this: see MS KB article 259893

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.
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:
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.
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
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

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.

EE Cleanup Volunteer
PAQed, with points refunded (250)

EE Moderator

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.