>>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.
>
>You can also use the "multipart/form-data" encoding to upload a file with native HTML (if you want to upload it to a web server process, and let that process deal with it).
>
>
>FORM NAME="frmUpload" METHOD="Post" ENCTYPE="multipart/form-data" ACTION="Upload.asp"
>
>INPUT TYPE="file" NAME="txtFileName"
>
>But decoding the file contents on the server process depends on what you are running on the server- using ASP, you do a BinaryRead on the Request object, and parse the contents, and write your file using some COM object with disk access rights.
>
>For details there are several articles at www.15Seconds.com that explain browser uploading...

Thanks, Erik - I'm not sure what's involved here - all I do from my end (I wrote the error handler for them) is check to ensure that IE is there, write the error log detail to a text file as well as to the logging database, and invoke their reporting class, which takes the file name and the object reference for the app object.