---
But your reply found me mouthing the word "HOW" for almost everything. As usual the documentation from MS is sparse, does not explain HOW changes may be made
----

Bernard, this is a Beta <s>. You don't have the docs from MS for reporting yet. You have *release notes*, which I believe are clear on this point, and beyond that, give you quite a bit of preliminary detail about Reporting which you can use until the docs are available to you.

----
HOW and where to make the change?
>A printable version would be a different XSLT of this XML,
Again HOW?
----

One of the things that the release notes give you is the interfaces for the various delivered FFC/ReportOutput classes. You will see there that the HTML Listener adds very little to the class tree; HTML output just leverages XMLListener's base format and XSLT-handling abilities, and adds a base XSLT transformation.

If you look at the XMLListener interface (as covered in the release notes), you will see that there is a .xsltProcessorUser property. This is where the XSLT that will be used at the end of a report run is stored if you turn .ApplyUserTransformToOutput on, which is what HTMLListener does.

You can examine this document, and you can change it, either by loading a new XSLT processor object or by loading a string holding a new document, or by loading a filename pointing to a file holding such a document. And yes there will be sample code to do this in the docs <s>.

But will you want to do so for every report, printing or not? I don't think so. I forgot to add this in my original message (wrote pretty late at night and am not home <s>), but one of the reasons you will find a textarea is useful for stretching data is to make sure that text wrapping comes out as expected when you report on a memofield.

As a result, the shipping default XSLT can expose a parameter for this purpose, leveraging XML's XSLTParameters collection for this purpose. (And, yes, there will be an example of setting such a parameter in the docs.)

Additional tests (in multiple browsers) and additional adjustments to the shipping XSLT are still underway. HTML can wrap with a newline character if you use a CSS white-space instruction, but browsers don't have to implement this particular instruction.

I'm sorry if you feel that my explanations are not helpful to you as they stand. As you see, no matter how much I say, there is always more that could be said and more avenues to explore <s>.

>L<