Ah, good guess on my part <g>. Don't worry about the utility then... unless it happens to you again. (please let me know if so)

I think you probably had *one* corrupted compile *once* that caused this to happen. Possibly a very long time ago, and it just didn't bother you before.

BTW: the release notes have fairly extensive information on FRX field usage, and we intend this information to go into the docs as well.

Now that FRXs are really extensible, now that fields not used directly by the engine can be interpreted by our code in ReportListeners, and now that other utilities can expect to use extension fields without losing their contents when the Report Designer writes out the FRX after a design session...

... everybody is probably going to have to be a little more careful about having "clean" FRXs than before.

This is to be expected -- and it's one reason why the supported and internal uses of the fields needs to be exposed and documented.

>L<