dynamic detailheight

rbuser

Hello
We are using RBuilder 5.56 and have a problem with the dynamic detailheight.
I'm using a memo with for example 5 Lines in the detailband.
Now the last Line of the memo overlapps into the next detailsection.

Any Idea what to do.

(detailheight property is set dynamic,bottom offset of the memo =0 other
propertys are standard)

thanks

digitalmetaphors

Is this in the screen preview? See the article below. Are there any
regions/ subreports with the memo inside of it? I am curious to what other
components are in the report. Take out all the other components, and let
only the memo print. Does the same behavior show up on the printer? If so,
then send us a demo to support@digital-metaphors.com


We have two choices when we create a preview - compose for the screen, or
compose for the printer. Most programs such as MS Word compose to the screen
when they create a preview. This makes for attractive previews but they tend
to
be inaccurate. And it means that they then compose again for the printer
when you print the document. Most of the time things will print effectively
similar to the preview, but we have seen many times when the printed output
was different - a word wrapped to the next line, or some such problem. If
you use a program meant for accurate page layout, such as PageMaker, you
will notice that the Page Setup dialog asks you for which printer you wish
to compose. When PageMaker displays a page, it may not look exactly how
you think it should, but you do get a preview where the element placement
is guaranteed to match the printed output's element placement.
We have chosen to follow this second model.

Note that when we say element placement, we are referring to X and Y
placement and not height and width. While the X and Y placement of
our previews will be accurate, the height and width of text elements
may vary based on zoom percentage. This is a normal artifact of
composing for the printer and not for the screen.

Your preview can not match your printed output. It will
differ in one of two ways:

1- It can look good on the screen, but items on the page may not
display in the same location they will when printed.
or
2- It can be less attractive, but items will display on the preview
exactly where they will when printed.

We give you the second because it is more accurate and more reliable.
Not to mention more in keeping with professional page layout products.


Cheers,

Jim Bennett
Digital Metaphors