Can't View or Print from a memo

[polman]

When trying to view or print a report from my database the text field
on my report, assigned to a Memo DataType table field in my database,
does not appears. Instead a little box appears in the report (where the
text from the Memo field should appeared) in most cases. Some times
the: <E>. This is not the case when I use the
Am I doing something wrong?
PS. With 'text' DataType' all text viewed and printed OK.

 

[Bill Mosca, MS Access MVP]

Can you view the memo field if you open the table directly?

 

[polman]

Bill thank you for your response.
Yes I do. The problem is on report (view or print).


Ï/Ç Bill Mosca, MS Access MVP Ýãñáøå:

 

[Bill Mosca, MS Access MVP]

A "little box" is a nonprintable character. Maybe the text box control just
can't display what is in the memo field, but if it shows in the table, I'm
stumped.

Try deleting the control and putting a NEW textbox with a NEW name on the
report to see if that helps. The control might be corrupt.

--
Bill Mosca, MS Access MVP


Bill thank you for your response.
Yes I do. The problem is on report (view or print).


Ï/Ç Bill Mosca, MS Access MVP Ýãñáøå:

 

[polman]

Sorry, that does not work either.
I know (unfortunately) about this non pretty, non printable
characters...
Maybe this information could help: I 'm not using the English version
of the Access and it seems like the case where a text for my language
(Greek) displayed with these little squares monsters... But not
exactly. The strange think is that there is only one of them no matter
how text is in memo text field (or table) and that is the case for the
English text too.
I hope that will help you to help me.
Thank you very much for your time.


Ï/Ç Bill Mosca, MS Access MVP Ýãñáøå:

 

[polman]

Bill thank you for your suggestion and the fact that you are stumped.
That was a reason to search more carefully on this
Actually I make a totally new record and this time I did not use the
query that I was using in the previous one. And... it works OK. I don't
know how the query got into play or in what way infects the field in
the report but it seems to be the reason for this odd behavior.
I will go through it and I hope to find a solution. Of course any
suggestion will be very helpful.


Ο/Η Bill Mosca, MS Access MVP έγÏαψε: