Hi Erik,

>The server should have absolutely no idea that the client closed the browser. Are you setting the referring variable to nothing before the script finishes?

I didn't write the ASP code, but it does something similar to this [I test this in Excel]:

Set oTest = CreateObject("webrep.pdfwriter")
nReportID = Worksheets(1).Range("B3").Value
cWhereClause = Worksheets(1).Range("B4").Value
cUserName = Worksheets(1).Range("B5").Value
cFileName$ = oTest.makepdf(nReportID, cWhereClause, cUserName)
Worksheets(1).Range("B6").Value = cFileName
Set oTest = Nothing

In ASP, it appears that if we close the browser during the call to oTest.makepdf [which can take up to 1 minute to complete], the script terminates and doesn't get to the line Set oTest = Nothing. I've tested this in the office and the code runs fine if we keep the browser open, but leaves the COM object in NT Task Manager if we close the browser prematurely.

I can get the same effect if I run the above macro in Excel and terminate Excel while oTest.makepdf is running [although I appreciate that may not be exactly the same as running it on a Web server.

Best.

Matt.