[Egon]

It's actually already implemented. There's a section in the script file where you can provide a link to your logfile.

Yeah, what he said.

You can link anything you want there. I happen to use it for the log file.

I thought about providing upload capability to my server for peoples' log files, but some of mine have been in excess of 300K, and I can't support the potential throughput., so...

Like AndyK pointed out, if you expose your log file via HTTP, you can link it. In theory, even if you don't have the logfile exposed externally, if you have a common share drive internal to your network, and put the link to that (for example: \\mymachine\logs\FAHLog.txt) the link would likely work for you (but fail for everyone else).

[andyk]

In theory, even if you don't have the logfile exposed externally, if you have a common share drive internal to your network, and put the link to that (for example: \\mymachine\logs\FAHLog.txt) the link would likely work for you (but fail for everyone else).

That's a really good point that bears repeating. I was only thinking of it in terms of accessing the log files remotely, but technically, you could provide local links to files that would be accessible to you if you clicked on them in Egon's interface locally from your domain/workgroup, and had file sharing permissions set up properly.

[HangThemHigh]

OK, miseed the link input in the script and I can understand you not wanting all that on your server. Thanks.