"Distributed" Text alignment in reports - Carriage return...??

[Guest]

I have a text box in a report linked to a 'memo' field in an access table.
The text is in the vicinity of 3kb so that returned on the report is quite
large, and forms the details section on the details for an estate agency. If
you right click the text box and open the properties window you can edit the
text alignment for the box. If you set the alignment to 'distribute' it
appears 'fully justified' as if in word. It does not however work in exactly
the same way as if there is one word left at the end of a paragraph the one
word is stretched accross an entire line - looking MOST untidy. Is there any
way I can incorporate a line of code, for example a carriage return to
eliminate this?

All replies gratefully received!

Many thanks

 

[Stephen Lebans]

Here is a snip from a previous post of mine on thsi issue:

1) A2K or higher supports a Distribute property for TextBox controls.
There is a bug/feature of the Distribute property whereby the last line
of the
paragraphi is fully justified even if it contains a single word.
Unfortunately there is no fix for this issue.


2) The Justify ActiveX control for Forms or Reports here:
http://www.lebans.com/xjustifytext.htm
Produce Fully Justified Text. Bind this control to your Memo field to
create professional looking reports! This is an ActiveX control that can
act as a Label or TextBox. This control has a RecordSource just like a
normal Access TextBox so it can be bound to a field or contain a
calculated expression. Developed for Microsoft Access97.
Requires VB6 Runtime files.


3) The RTF ActiveX control for Forms or Reports here:
http://www.lebans.com/richtext.htm
RTF2 control is an ActiveX RTF solution written in VC++. The RTF2
control is a complete editing/printing solution for Access 97 or higher.
Autosizing of the RTF2 control is supported for A2K or higher.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[JeffG]

Just ran into this issue and was searching the web trying to find a resolution. I'm using Access 2013 and when I changed the Text Format from the default of Plain Text to Rich Text the problem went away! While I was researching someone had posted somewhere else that changing to Rich Text creates its own issues. Not sure if that still applies in Access 2013 or what those issues might be, but this worked for me and will hopefully benefit someone else.