Memo Field Text Hidden

[Larry Bohen]

I maintain our product db on Access 2003 SP2. One of the memo fields
contains the description of the audiobook and can contain as many as 5000
characters. Most of the memo field descriptions are visible all the time,
but I have noticed for some time that some description memo fields are
hidden unless the field is selected. I discovered this AM, that if I reduce
to length of the text, the memo field is again visible when it is not
selected.

Memo fields do not have a maximum number of characters (like text fields do
= 255). Is there a maximum number of characters for a memo field, that once
exceeded, the text will be hidden unless the field is selected?

 

[tina]

i've never experienced this behavior, but you might check the following: in
the textbox control, is the EnterKeyBehavior property set to NewLineInField?
and is the ScrollBars property set to Vertical?

btw, a Memo field *does* have a maximum number of characters: 65,535. with
the following caveat from Access Help: "If the Memo field is manipulated
through DAO and only text and numbers [not binary data] will be stored in
it, then the size of the Memo field is limited by the size of the database."

hth

 

[Guest]

Larry:

The behaviour you are experiencing sounds rather different, but there is a
known bug associated with memo fields which can unpredictably cause the text
to appear to be truncated. This can be the case in a table in raw datasheet
view where the data has been imported from another format (I first
encountered it with imported dBASE data), but it can also be the case in
forms or reports with native Access data if the control is added to the form
or report by dragging from the field list. I think it can also arise with
forms created with the form wizard.

The solution is to add a text box to the form or report from the tool box
and set its ControlSource property to the name of the memo field. Normally
the text box's EnterKeyBehavior property would, in a from, also be set to New
Line in Field.

As I said, your behaviour differs from this, and is something I've never
seen, but its possible the underlying cause might be similar, and require the
same solution.

Ken Sheridan
Stafford, England