Word wrapping problem

avl

New member
Local time
Today, 23:02
Joined
Apr 6, 2005
Messages
6
Hi everyone,

I have a small but nasty problem with a text box in Access2k. The text box shall display the name of a person in the form <Last Name>, <First Name>. Hence I fill my text box with: =[NName] & ", " & [VName], where 'NName' is the Last Name, and 'VName' is the First Name of that person. When some person has a rather long name, the text box truncates the name right in the middle of a letter! I.e. even though I set 'Can Grow/Can Shrink' to 'Yes' in both the text box and the detail section properties, I doesn't wrap the whole field. But it does wrap it only if the last name is too long, e.g. the text 'Goddamnlongname, A.' would be displayed as 'Goddamnlongname,<newline> A.' , or 'Goddamn-Longname, A.' displays as 'Goddamn-<newline>Longname, A.', which is totally oK. If however, the last name fits into the textbox, the first name gets chopped off right in the middle. I have attached a small JPG to illustrate what I mean. I have cut out two names from the report, the first appears truncated, while the second is wrapped properly.

I had trouble like this before and could always manage it with CanGrow/CanShrink etc. But this time it doesn't do the trick. Is it due to the concatenation? Any suggestions appreciated.

TIA,
Alex
 

Attachments

  • name.jpg
    name.jpg
    19.4 KB · Views: 203
Have you tried to concatenate them in the underlying query?
 
Thanks for the suggestion. Even though it ain't perfect, I appreciate it very much. After doing what you proposed I had to fiddle around with the width of the text box to make it appear oK. When too narrow or to wide, it wrapped the text at the wrong position, i.e. in the middle of a word. And who wants to see his/her name mangled like this in a directory? :p

It works fine with the current set of names. I just hope it will be oK with future entries. I'm just wondering why wrapping doesn't work with concatenated fields, as this actually should be easier to do for Access than with one single field, one would think. But who would attribute common sense to Access, on the other hand? :p

Again, thanks for your help.
Alex
 

Users who are viewing this thread

Back
Top Bottom