Emerald does that in one of two cases:
1) You have debug mode on.
2) An SQL Statement failed.
The first is a result of you having debug mode on when you shouldn't. :)
Debug mode should NOT be used unless you are haveing a problem and
support
wants to get more information about it.
The second allows someone to see what the last SQL Statement was during
a failure (you can go plug it into isql_w and see the full problem).
I'll look into adding an option for the second one that is by default
off.
--Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list, including removal,please see http://www.iea-software.com/maillist.html