Excuse me, Bill?

Which "mondo workaround" are we talking about exactly?

And just btw why exactly should ANSI Windows (1252) be what we work from?

Look: the gentleman is from Malaysia so I'm guessing his codepage is 936, which would make his fontcharset 134. When I use this script and a font supporting it for his report, it looks right, both in traditional output results and in the HTML.

In fact, if he confirms I've guessed right, and if he gives me permission to share his data, I'll send you the HTML (all 372 pages'worth of the report ).

It is perfectly appropriate to assign script on a layout-object level for reports (although of course you can do so on a report-level as well).

I don't see anything remotely like a workaround about it. Bear in mind that expressions in a report may have no relationship to any DBF marked with a codepage, or they may be derived from *several* DBFs, marked with different codepages.

All should show properly in the same report.

Working in a single codepage, whether 1252 or any other, doesn't cut it.

>L<