Torgny, thank you so much for doing this!

When I looked at your information, I did not even have to compile to see where the issue was, and why I could not reproduce it earlier.

The required factor is an #INCLUDE file in the DataEnvironment code!

After looking at your report quickly, I simply looked at one of my reports with an #INCLUDE and saw the same effect immediately.

Here's what I can do now:

1) verify whether the compiler has to do this or not. It may have to.

In your report, you don't realize this but in my report, my #INCLUDE has some subsidiary #INCLUDES, like this:

* COVERAGE.H

*&* Coverage character constants for log and parsing:
#INCLUDE COV_CHAR.H

*&* Coverage localized strings (may use some constants above):
#INCLUDE COV_LOCS.H

*&* Coverage common dialog component constants:
#INCLUDE COV_DLGS.H

*&* Coverage specs & requirements:
#INCLUDE COV_SPEC.H

*&* Coverage registry object constants:
#INCLUDE COV_REGS.H

*&* Coverage tune-able options:
#INCLUDE COV_TUNE.H

When I look in the FontFace field, I see that, this is where the compiler is handling the included #INCLUDEs.

2) Once verified, if it is not necessary it will be fixed. If it is necessary, HTMLListener can account for it -- Actually XMLListener will account for it by removing this information as it does the other compiled code information.

I really appreciate your patience.

>L<