Home End User
New Blog Posts: Merging Reports - Part 1 and Part 2

Memo field breaks a word at strange places

edited August 2003 in End User
Hi,

RB Enterprise 6.03

When using a DBMemo field words are broken at the strangest places to
continue the text at the next line. Would it be possible to specify that
words can't be broken?

regards
Paul Sjoerdsma

Comments

  • edited August 2003
    On the memo in this case, WordWrap should be true and CharWrap set to false.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited August 2003
    In article <3f438c25$1@dm500.>, "Jim Bennett \(Digital Metaphors\)"
  • edited August 2003
    WordWrap is implied on a Memo. CharWrap is the only property you can set to
    affect this behavior. Do you have any control characters in your text, such
    as #13#10 (CarriageReturn and LineFeed)? Can you save this memo record data
    to ascii text and load it into a TppMemo? Then send this simple report that
    shows the problem to support@digital-metaphors.com and I'll see what could
    be causing the problem. It should not be char wrapping if you have CharWrap
    set to false.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited August 2003
    Hi Jim,

    I can only reproduce this when using a DBMemo.
    The underlying field from the datapipeline is a SQLServer field of type
    image.

    Any way i can send you an example of this ??

    regards
    Paul

    In article <3f44dcce$1@dm500.>, "Jim Bennett \(Digital Metaphors\)"
  • edited August 2003
    Using Delphi code, can you stream the image field to a file stream so you
    can see it in pure ascii text format? I suspect there are control characters
    in there somewhere which are causing a problem with our word wrapping logic.
    You should be able to reproduce this with a TppMemo since the TppMemo and
    TppDBMemo rely on exactly the same wordwrapping logic.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited August 2003
    Jim,

    Problem solved by deleting the DbMemo component and adding a new one.
    Probably one of those "comsic ray interference" problems .....

    Thanks
    Paul

    In article <3f462d46$1@dm500.>, "Jim Bennett \(Digital Metaphors\)"
This discussion has been closed.