Controlling Microsoft Document Box

[Pat Flickner]

I have a process that creates an Excel spreadsheet for download which can be quite large depending on the parameters selected. The problem is, when the file is large and the user chooses to open the report right from the document save popup instead of just saving it, it eats up a huge amount of memory on the server while it's passing the data to Microsoft Excel. The question I have is, can I force the popup to disable to Open button? I haven't been able to find anything on this specifically. Thanks.

[Ulf Dittmer]

This sounds strange to me. Once the file is streamed to the client, nothing the user does should influence memory consumption on the server. How did you determine that that's the cause?

[Pat Flickner]

Pretty much, I was watching the server's memory (we have a web page that we created awhile ago that shows how much memory the server has and how much is currently in use) and saw it spike when I did anything with the Excel. It was very short for doing a Save, but opening it directly from the MS popup (clicking the Open button) took a long time, so it is streaming directly to Excel rather than just a straight download. See, it hasn't completed the stream yet when it's doing a direct download to Excel from the server; it seems to be actually using the server to build the Excel format for Excel. If it downloads to the PC via a Save, this isn't an issue -- brief spike, albeit not as severe, and then it's done.