Is there a limitation on the number of characters that a report text
box can display?
The text box is in the report header. It won't display more that 247
characters of text, including spaces.
CanGrow is "Yes" in the case of both the text box and the header. Even
if you make the box plenty big the characters simply don't show,
leaving white space in the box.
I did various experiments to confirm this. Also brought the next part
of the text right up adjacent to make sure there were no invisible
unprintable characters messing with it.
Thank you, I am going crazy!
-plh

More Information:
The text box is taking its information from one column of a Drop-Down
box's query. That is, the data in the text box is:
=[cbxManuscript].[Column](4)
The data field accessed by drop down box cbxManuscript is of the memo
type.
The drop down box cbxManuscript is in the report detail, while the
text box is in the report header.
I tried making the box various sizes, putting in a brand new text box
(same result, exactly), even changing the widths of the drop down box
columns.

More information than you require (probably):
The whole SQL for cbxManuscript is as follows
SELECT DISTINCTROW tblManuscripts.ManuscriptCNum,
tblManuscripts.PartNumber, tblManuscripts.ProgramNumber,
tblManuscripts.PartName, tblManuscripts.Notes, tblManuscripts.ZSet,
tblManuscripts.IsLeft, tblColletShapes.ColletShape,
tblColletTypes.ColletType, tblCollets.ColletSize, tblCollets.TNumber,
tblManuscripts.Fixture, tblManuscripts.IllustrationHyperlink,
tblCollets.Fraction, tblCollets.OKNum FROM tblColletTypes INNER

tblManuscripts.Notes is the memo field

On Wed, 6 Oct 2010 11:09:46 -0700 (PDT), plh <(E-Mail Removed)> wrote:

>Is there a limitation on the number of characters that a report text
>box can display?
>The text box is in the report header. It won't display more that 247
>characters of text, including spaces.
>CanGrow is "Yes" in the case of both the text box and the header. Even
>if you make the box plenty big the characters simply don't show,
>leaving white space in the box.
>I did various experiments to confirm this. Also brought the next part
>of the text right up adjacent to make sure there were no invisible
>unprintable characters messing with it.
>Thank you, I am going crazy!
>-plh
>
>More Information:
>The text box is taking its information from one column of a Drop-Down
>box's query. That is, the data in the text box is:
>=[cbxManuscript].[Column](4)
>The data field accessed by drop down box cbxManuscript is of the memo
>type.
>The drop down box cbxManuscript is in the report detail, while the
>text box is in the report header.
>I tried making the box various sizes, putting in a brand new text box
>(same result, exactly), even changing the widths of the drop down box
>columns.
>
>More information than you require (probably):
>The whole SQL for cbxManuscript is as follows
>SELECT DISTINCTROW tblManuscripts.ManuscriptCNum,
>tblManuscripts.PartNumber, tblManuscripts.ProgramNumber,
>tblManuscripts.PartName, tblManuscripts.Notes, tblManuscripts.ZSet,
>tblManuscripts.IsLeft, tblColletShapes.ColletShape,
>tblColletTypes.ColletType, tblCollets.ColletSize, tblCollets.TNumber,
>tblManuscripts.Fixture, tblManuscripts.IllustrationHyperlink,
>tblCollets.Fraction, tblCollets.OKNum FROM tblColletTypes INNER
>
>tblManuscripts.Notes is the memo field

The limit is not the Textbox, it's the Combo Box from which you're drawing the
data. You cannot put a Memo field into a Combo Box column and expect it to
return all (potentially) billion characters of the memo!

Try changing the control source of the textbox to something like

=DLookUp("Notes", "tblManuscripts", "ManuscriptCNum = " & [cbxManuscript])

and thanks for posting the details that allowed me to give a better answer!
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/For...-US/accessdev/
http://social.answers.microsoft.com/.../en-US/addbuz/
and see also http://www.utteraccess.com

John W. Vinson <jvinson@STOP_SPAM.WysardOfInfo.com> wrote in
news:(E-Mail Removed):

> The limit is not the Textbox, it's the Combo Box from which you're
> drawing the data. You cannot put a Memo field into a Combo Box
> column and expect it to return all (potentially) billion
> characters of the memo!

Call me crazy, but combo boxes don't belong on reports at all.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On 8 Oct 2010 01:21:32 GMT, "David-W-Fenton" <(E-Mail Removed)>
wrote:

>John W. Vinson <jvinson@STOP_SPAM.WysardOfInfo.com> wrote in
>news:(E-Mail Removed):
>
>> The limit is not the Textbox, it's the Combo Box from which you're
>> drawing the data. You cannot put a Memo field into a Combo Box
>> column and expect it to return all (potentially) billion
>> characters of the memo!
>
>Call me crazy, but combo boxes don't belong on reports at all.

eep! Durn straight - Thanks, David, I didn't even pick up that this was on a
report.

Given that, forget the DLookUp too - just join the tables in the report's
Recordsource query.
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/For...-US/accessdev/
http://social.answers.microsoft.com/.../en-US/addbuz/
and see also http://www.utteraccess.com