[quote user="Anaglypta"]
Greenman,
You could always look at the log files to review the history. I use a remote desktop connection to the server, and open the log file in a text editor (Textpad). This also has the advantage of being able to review all activity in a log since its creation (usually midnight), where the modules' window only holds information up to buffer full when the oldest lines are removed to make way for the newest.
John.
[/quote]
Thanks for responding. I do keep full transaction logs, but I only use those for troubleshooting. All I need is a summary view which I can get by scrolling up through the list of previous transactions. I only need to get an idea of how Mercury/32 is functioning. If I see issues, then I will move onto the logs themselves.
It would make my life easier if autoscroll could be disabled in a future edition, or perhaps if a summary report could be generated for a particular module.
[quote user="Anaglypta"]
<P>Greenman,</P>
<P><SPAN style="FONT-SIZE: 10pt">You could always look at the log files to review the history. I use a remote desktop connection to the server, and open the log file in a text editor (Textpad). This also has the advantage of being able to review all activity in a log since its creation (usually midnight), where the modules' window only holds information up to buffer full when the oldest lines are removed to make way for the newest.</SPAN></P>
<P>John.<SPAN style="FONT-SIZE: 10pt">&nbsp;</SPAN></P>
<P>[/quote]</P>
<P>Thanks for responding. I do keep full transaction logs, but I only use those for troubleshooting. All I need is a summary view which I can get by scrolling up through the list of previous transactions. I only need to get an idea of how Mercury/32 is functioning. If I see issues, then I will move onto the logs themselves.</P>
<P>It would make my life easier if autoscroll could be disabled in a future edition, or perhaps if a summary report could be generated for a particular module.</P>