That helped. I got rid of the scrollbars. The only remaining problem is that some of the fields are getting cut off at the bottom. That is, the last row of text in a field is being clipped. Any ideas?

I do have an idea. I have an idea that you may have realised why TextAreas are used by default! ;-)

Tamar, you didn't "get rid of the scrollbars". What you did is conciously switched to a *different* mechanism to render HTML code for the stretching field/Expressions.

Take a look at the HTML result. You'll see that hard carriage returns are now translated to BR tags in order to get them to look like how a user would expect. Browsers have different ideas about the spacing of BR tags - it is not the same as the normal line spacing. Things get more strange with different font sizes.

Both mechanisms have trade-offs. One of the mechanisms is more likely to ensure that all data is visible in the output, and that is the one that is used by default. TextAreas respect the hard spacing.

Anyone is free to replace the XSLT with their own, improved version, to yield HTML that looks better. They can do this when they understand the nature of the reports they are rendering, and are able to tune the HTML generation code more tightly to their FRX layouts.

The XSLT that is provided out of the box must be more generic, and produce satisfactory results for EVERY report that ANYONE might throw at it.

Frankly, I'm in awe of the fact that HTML output (via the default, provided, XSLT transform) works as well as it does. It's so good that users don't even see the magic involved.

One last comment: In Sedna, you will be able to attach CSS styles to field/expression controls and this might let you force a slighly smaller font size and therefore avoid the truncated text that you see...

- Colin