Memo field in the report. Does it grow?

[Lifeseeker]

Hi,

I have a memo field to be displayed on the report, and it contains the history.

If the history gets huge down the road, will the report contain all the texts in the memo field?

If I set the Grow property to "yes", will that do the trick?

Thank you

 

[boblarson]

You have to set the Can Grow property of BOTH the text box AND the section where the text box resides. However, the binding of the text box will ONLY show at max 65,535 characters. To get more you have to use VBA to assign for viewing or to write to it then you can have approx 2 million characters.

 

[vicsalt]

Ive had the same issue, people keep spouting how a memo will hold over 64K characters, when infact it only displays 255!. I dont understand the point.

I created a table using some memo fields, then a form to allow users to enter data.
Then I found out the memo fields are restricted to 255 characters and its seems thier is nothing you can do bout this (after scanning Internet for several hrs)

So I changed the fields in my tables to OLE Objects then modified my form, adding text boxes (which will hold stacks of characters!) I then assosiated my text box with the relevant control fields from my table, GREAT.

However, once the form is complete I generate a report which is emailed off. The corrasponding fields on the report only show the 1st 255 characters .

I have the properties set to Can Grow, but makes no differance
Help Please

 

[boblarson]

Ive had the same issue, people keep spouting how a memo will hold over 64K characters, when infact it only displays 255!. I dont understand the point.

I don't know where you got that but memo fields do, in fact hold 65,535 characters when manually typed in or retrieved by the normal form process. They can hold up to 2 million characters when used with VBA.

I created a table using some memo fields, then a form to allow users to enter data.
Then I found out the memo fields are restricted to 255 characters and its seems thier is nothing you can do bout this (after scanning Internet for several hrs)

Again, I don't know what is going on in your form, but I would like to see a copy of the database because there is plenty you can do, and they do hold more than 255 characters. You must have something set up INCORRECTLY.

So I changed the fields in my tables to OLE Objects then modified my form, adding text boxes (which will hold stacks of characters!) I then assosiated my text box with the relevant control fields from my table, GREAT.

Not good - it is not the way to go.

However, once the form is complete I generate a report which is emailed off. The corrasponding fields on the report only show the 1st 255 characters .

Again, you have something set up incorrectly and if you can post a copy of the database I'm sure I can tell you what is wrong with it.
I have the properties set to Can Grow, but makes no differance

 

[lcook1974]

I had the same problem with memo field before. What I realized is that I had a SELECT DISTICNT in a query...When that was there it only showed the 255 characters. After I took that off the memo field displayed as it should.

You may want to check that out. Select distinct doesn't play nice with memo fields greater that 255 characters.

 

[boblarson]

That's where this Allen Browne article comes in handy:

http://allenbrowne.com/ser-63.html

 

[gopherking]

Just to add on to this thread just in case anyone else comes across this as well, I had a report based on a Query that pulled from another Query. My Memo fields were in the first query, which at that point they were truncated. In order for my memo fields to not be truncated to 255, I had to add the initial table where the memo fields originated from into the Query that my report was generated from and add the fields into the query at that point. It seems a little redundant to requery the same Table more than once, but it got around the truncation and didn't impact the processing of the report at all.

So, to sum up, if you are going to have Memo fields used in a report that is pulled from multiple-level queries, make sure you add the Memo fields into the final query before it is pulled into your report ... it will save you from getting some grey hairs!

 

[boblarson]

Just to add on to this thread just in case anyone else comes across this as well, I had a report based on a Query that pulled from another Query. My Memo fields were in the first query, which at that point they were truncated. In order for my memo fields to not be truncated to 255, I had to add the initial table where the memo fields originated from into the Query that my report was generated from and add the fields into the query at that point. It seems a little redundant to requery the same Table more than once, but it got around the truncation and didn't impact the processing of the report at all.

So, to sum up, if you are going to have Memo fields used in a report that is pulled from multiple-level queries, make sure you add the Memo fields into the final query before it is pulled into your report ... it will save you from getting some grey hairs!

Yeah, it basically comes down to that you can't have any criteria on the query where the memo field is included. So, if you need to have criteria then put all fields EXCEPT the memo field into the query and put the criteria there and then add that query into another query and with the table again, linked to the appropriate field(s) and then include the memo field from the table.