I had the same issue when I migrated to U9. Compuware told me that in the meta ( = internal ) character set Uniface reserves the first 32 characters (0-31 decimal) plus the last character (127 decimal) for its own use (documented in the Ulibrary, Meta Character Sets). So decimal character 13 (carriage return)  you are inserting is a reserved character in Uniface and shouldn't be used otherwise. They say that it may be that in Uniface 8 it went fine, but the encoding mechanisms have been changed in Uniface 9 ( added Unicode support) and they don't accept it as a migration bug since it is documented that these characters are reserved.

I ended up using a MS Word COM workaround to create a blank Word document and send the entire string to Word -- I can forsee this workaround for people on non-Microsoft systems but has been working fine for me.

Regards,

Larry

Thank you Larry,
I´ll try that solution.

Regards,

Rafa.

Are you guys talking about the same thing here? Because I wander.

Anyways, what triggered me to also provide some info is the fact that you're using the web. I do not know weather this is your problem but do realize that CRs are only used to format the source HTML and are not interpreted by the browser (ignored). So any CRs in your data with the purposeto be shows as HTML will have this problem.You have to replace the CR with the HTML counterpart <br>.
If you are using DSPs, the StaticText widget will do this automatically.

Regards,
Gerton

<mode=smart_ass>

<br/>

</mode>