>>>>Hi Ed,
>>>>
>>>>>If the user doesn't want to report the error, and there's no automatic means of reporting the error "up the ladder" to you, there's little that can be done.
>>>>
>>>>I've toyed with the idea of having error reports automatically e-mailed to me, but haven't actually tried implementing it yet.
>>>
>>>You could automate it easily enough, as long as there was a system that could do email that could see the log; you could have Outlook for example check to se if the file were there once a day or something, and if some, send it out by email. No email obviously means this doesn't work, which is why I said no automatic means above.
>>>
>>>One interesting thing added to a system I've been working on is the error handler popping up a button to give the option of having it start IE and connect to the vendor's web site to report the error. Works very neatly.
>>
>>We actually have a menu bar option, "Report a bug", that opens a URL with a form were the users type the problem. The form creates an eMail that is forwarded to us. It works really nice: 30+ errors reported, but no error log attached!
>>
>
>We use the InternetExplorer.Application object and manipulate the DOM directly - there's no user interaction at the web site. Depending on the capabilities at the server end, any number of things may be doable - send the report as a response packet, ftp, etc. are options.

Ohhh, didn't knew it was possible to use OLE automation with IE. Is it documented in the MSDN library? FTPiing is a nice feature...guauu!

Nelson