field is cut off

[JohnE]

Greetings. I have a query in which other queries are joined together. These
other queries are pulling into the main query a comment field from a table
that are of different topics. The table datatype is memo. On the report the
long comments are cut off. The report field is set to grow. On the main
query it shows the long comments as cut off. I went to the query that brings
in the different comments and it too shows the long comments cut off. Upper
management will be screaming about this, no doubt. Why is the comment
getting cut off in the queries? Is there a way to fix it?
Thanks in advance for any assistance.
*** John

 

[Rick Brandt]

Greetings. I have a query in which other queries are joined
together. These other queries are pulling into the main query a
comment field from a table that are of different topics. The table
datatype is memo. On the report the long comments are cut off. The
report field is set to grow. On the main query it shows the long
comments as cut off. I went to the query that brings in the
different comments and it too shows the long comments cut off. Upper
management will be screaming about this, no doubt. Why is the
comment getting cut off in the queries? Is there a way to fix it?
Thanks in advance for any assistance.
*** John

If you group on the memo, sort on the memo, or apply a format to the memo,
it will be truncated at 255 characters. Are you doing any of those?

 

[JohnE]

Rick, thanks for the relpy. Yes, the Group By is on the memo field. It is
also on the others inside the query. Is there a way around it.
***John

 

[Rick Brandt]

Rick, thanks for the relpy. Yes, the Group By is on the memo field.
It is also on the others inside the query. Is there a way around it.

Use First() instead for the memo field.

 

[JohnE]

Rick, I went to one of the queries pulling in the memo field and changed it
to First and also went to the main query and changed it to First there as
well. It is still getting cutoff at 255.
Any other thoughts on this? I am at a loss of what to do.
Thanks.
*** John

 

[Rick Brandt]

Rick, I went to one of the queries pulling in the memo field and
changed it to First and also went to the main query and changed it to
First there as well. It is still getting cutoff at 255.
Any other thoughts on this? I am at a loss of what to do.
Thanks.
*** John

I just ran a test in Access 2000 and using First solved the problem for me.
My test memo with around 1000 characters comes through in its entirety if I
use First.

Are you sure you don't have an input mask or format property (possibly
inherited)?

 

[JohnE]

Sorry not to get back sooner. Got sidetracked with some other duties. There
is no input mask for the memo field. As for formatting, there is a
conditional format for when the field has focus it turns yellow so the user
knows what field they are on. The table properties are clean for any inputs
or formatting.

I went into the qry that pulls out the memo and changed the qry field from
group by to First. I then went to the main qry and changed the group by to
First. So the name it is given is First of First .... Even after changing
the report field names it still came up cutting off at 255.

Puzzling to say the least. Either way, thanks for the replies. One last
suggestion?

*** John

 

[Duane Hookom]

PMFJI,
Could you share the SQL view of your queries?

 

[Gail]

Hi Duane,

I've got a similar problem to John, a query that truncates a memo field. I
have no sort on the memo field, input mask or formatting. I'm stuck
shortening the memo to 255 characters because I can't figure this out. Any
ideas would be greatly appreciated!

Gail

 

[Duane Hookom]

Is the field truncated in your query? I expect your query might include
"DISTINCT", "GROUP BY", or similar.