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

Font Problem

edited August 2003 in General
When using Arial 10 point (defaulted by report builder). When fields or
labels are placed on the band, the field height is just a bit to small. It
cuts of the bottom of g's, etc. Is there any way to set the default height
of the fields and labels and report builder adhere to that?


Thanks

Comments

  • edited September 2003
    Hi Gary,

    Sometimes when using the Report Designer, the bottoms and right sides of
    TppLabels can appear to be cut off but this should not be the case when
    previewing and printing the report. Are the bottoms of the g's and y's
    being cut off in the previewer?

    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited September 2003
    Yes they are being cut off both for preview and paper. When any
    modification is done to the field it resizes it one pixel too small in
    height. It is really a pain to select modified fields and resize them
    manually.

    Thanks in advance for looking into this.


  • edited September 2003
    Hi Gary,

    I am a bit unclear on how to recreate this problem. What type of
    modifications are you doing to the fields on the report? Do they display
    correctly when you initially place them on the report? Please provide me
    with the exact steps you take to see this behavior so I can recreate it on
    my machine.

    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited September 2003
    1. Place ppDBText component on the form with Arial 10 points (default).
    2. Set the pipeline and all that good stuff
    3. Run the report with some g's in the data, the bottom part of the g is cut
    off.

    I tried this again with pplabels and they work ok. The design time interface
    cuts the g's off, but the report looks ok. It appears to only be a problem
    with ppDBText component.


  • edited September 2003
    Hi Gary,

    Try setting the DBText.AutoSize property to True and see if that gives you
    the results you are after.

    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited September 2003
    That will not be a viable option. This will cause stretching of fields and
    the report will not be presented professionally to the end user. Have you
    verified the problem?

    Thanks


  • edited September 2003
    Hi Gary,

    Using the end user solution, I followed your exact steps and was unable to
    recreate the problem. Inside the preview, the "g's" appear to be cut off
    but when I print to the printer, everything looks fine. This may be a
    printer driver problem as ReportBuilder uses the default printer driver to
    render all components on the screen and on paper. Try downloading the
    latest printer driver for the printer you are using and see if that helps.
    Also, you might try printing to a different printer and see if the results
    change. See the article below for more information on why the preview might
    not match what gets printed.


    -----------------------------------------------------
    Article: Why Preview may not Match Printed Output
    -----------------------------------------------------

    ReportBuilder uses the Printer device context to perform all calculations
    required to generate the report pages. This includes measuring text,
    wrapping text, and calculating the vertical page space required by a
    stretchable component such as a memo.

    Using the Printer device context results in a very high degree of accuracy
    when printing to the printer. For report Preview, all page elements must be
    scaled back to the screen. A typical printer has a resolution of 600 pixels
    per inch (or more). A typical screen has 96 pixels per inch. Thus there is
    some loss of fidelity in rendering to the screen.

    For multi-line text such as memos, ReportBuilder sometimes shrinks the font
    size for the preview so that the rendered text can fit within the required
    vertical page space. Even when True Type fonts this is sometimes necessary.

    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
This discussion has been closed.