Print a Memo Field in Access 2000 Report

[Guest]

How do I force the printing (display) of the complete contents of a memo
field in an Access 2000 report? It looks like it's using the size
restriction of a Text field and some of the information is not printed. (I'm
not using the whole field, but am using more than 255 characters in some
cases.)

 

[Marshall Barton]

How do I force the printing (display) of the complete contents of a memo
field in an Access 2000 report? It looks like it's using the size
restriction of a Text field and some of the information is not printed. (I'm
not using the whole field, but am using more than 255 characters in some
cases.)

Memo field truncation is caused by something in the report's
record source query that needs to compare the values in the
field. Using a memo field in the Order By or Group By
clause is a common cause. Using the DISTINCT or UNION
operations are others.

Another cause is specifying a Format property for the memo
field's text box.

 

[Guest]

I have the same issue, and in my particular case, it is because the report is
based on a Select Query where the Memo field is set up as a "Group By"...
There is no other way to set up this query, so what I need to know is, is
there any way to display the entire contents of the data in the memo field
from a Select Query?

-LM Comeau

 

[Marshall Barton]

As I said before, the issue is caused by using the memo
field in the Group By clause. When you think about it,
there is no logical reason to use a memo field in a Group By
clause. If you really need the large size of a memo field,
then each one is practically guaranteed to be unique and
grouping on unique fields in a non-operation.

Typically, the memo fields can/should be retrieved either in
the report (e.g. =DLookup expression) or in an additional
query that Joins the grouping query to the table with the
memo field.

 

[Guest]

Thanks, Marshall, for your comments. Obviously you're much further advanced
in your understanding of Access than I. My report requires the memo field as
the "Description" of a unique code number and there was a LOT of grouping
going on. The easiest way to include the proper description with it's code
was to put the whole thing together in that Query. There's no doubt that it
may not have been the most elegant way to do it, but I still need that
Description.
Fortunately, LMC posted the answer on his similar question.
Unfortunately I don't have a local contact that I can talk to
voice-to-voice, so I'll continue to learn about Access by reading, by trial &
error and by asking people with deeper knowledge.
Thanks again.

As I said before, the issue is caused by using the memo
field in the Group By clause. When you think about it,
there is no logical reason to use a memo field in a Group By
clause. If you really need the large size of a memo field,
then each one is practically guaranteed to be unique and
grouping on unique fields in a non-operation.

Typically, the memo fields can/should be retrieved either in
the report (e.g. =DLookup expression) or in an additional
query that Joins the grouping query to the table with the
memo field.
--
Marsh
MVP [MS Access]

I have the same issue, and in my particular case, it is because the report is
based on a Select Query where the Memo field is set up as a "Group By"...
There is no other way to set up this query, so what I need to know is, is
there any way to display the entire contents of the data in the memo field
from a Select Query?

 

[Marshall Barton]

Thanks, Marshall, for your comments. Obviously you're much further advanced
in your understanding of Access than I. My report requires the memo field as
the "Description" of a unique code number and there was a LOT of grouping
going on. The easiest way to include the proper description with it's code
was to put the whole thing together in that Query. There's no doubt that it
may not have been the most elegant way to do it, but I still need that
Description.
Fortunately, LMC posted the answer on his similar question.
Unfortunately I don't have a local contact that I can talk to
voice-to-voice, so I'll continue to learn about Access by reading, by trial &
error and by asking people with deeper knowledge.

If that actually does what you want, then I guess you have a
far more complex query than I had assumed.

And yes, we all learn a ton of things in the newsgroups.
Amazing how much knowledge comes together here.

Keep after it, it gets easier the longer you work on it ;-)