I have a column on a report for an email field. The fit on that column is set to wrap. Since the email field doesn’t have any spaces in it, it doesn’t wrap, just truncates.
Is there any way to force L&L to wrap even without any spaces in the field?
I guess I could put spaces in the email field after every period (.) which would allow it to wrap, but it would look funny for emails that aren’t long enough to wrap.
Looks funny in the editor, but it allows the EMAIL field to wrap after
‘.’ and before ‘@’.
(You can do the same in your code with all non-alphanumerical
characters, might be better than just allowing the address to wrap at
the two characters in the example above)
Paulchen
“Lane Coddington” <lane@volsof…> wrote in message
news:27278111220080046@combit.net…
I have a column on a report for an email field. The fit on that
column is set to wrap. Since the email field doesn’t have any spaces
in it, it doesn’t wrap, just truncates.
Is there any way to force L&L to wrap even without any spaces in the
field?
I guess I could put spaces in the email field after every period (.)
which would allow it to wrap, but it would look funny for emails
that aren’t long enough to wrap.
It’s interesting that I first inserted the two spaces into the original field before sending it to L&L, but that didn’t work. All the double spaces appeared on the report. It only worked when I made the replacement to the field within the report’s design that L&L correctly removed the double spaces from the final report. I wonder how L&L knows the difference.
I see that you help a lot of people in these forums. Do you work for Combit?
Thanks again.
Lane Coddington
Yes. Use LL_CHAR_PHANTOMSPACE (which is 2 by default).
Actually I do help them (irregularly) in this newsgroup, as I think
it’s worthwhile for their product. They also helped me several times
in an unbureaucratic way, so that’s my way of returning what I get.
I am pretty experienced with List & Label, as I use it more or less
intensively over a decade now - disciple of the first days… And as
I know how invaluable it is to get help or ideas of someone, and when
I find some time, I have no problem sharing my experiences, although
sometimes it’s just something that lingers far in the back of my head,
just to be re-activated
BTW: if you modify the email field in your program to surround all
non-alphanumeric characters, remember to add an unmodified field in
case someone wants to use it as link or such - the PHANTOMSPACES would
cause grief
Paulchen
“Lane Coddington” <lane@volsof…> wrote in message
news:4452111122008162336@combit.net…
Thank you, it worked perfectly.
It’s interesting that I first inserted the two spaces into the
original field before sending it to L&L, but that didn’t work. All
the double spaces appeared on the report. It only worked when I made
the replacement to the field within the report’s design that L&L
correctly removed the double spaces from the final report. I wonder
how L&L knows the difference.
I see that you help a lot of people in these forums. Do you work for
Combit?
Thanks again.
Lane Coddington
Yes. Use LL_CHAR_PHANTOMSPACE (which is 2 by default).