"stephen" <st********@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
[top-posting corrected]
>>I created an ExcelObject in memory
If this approach is not efficient,
Not only is it not efficient, it is not recommended or supported by
Microsoft because Excel (and the rest of Office) wasn't designed to be
used in this way:
http://support.microsoft.com/default...US;q257757#kb2
http://support.microsoft.com/default.aspx/kb/288367
>>Is there any other efficient approach?
http://www.aspose.com/categories/fil...a/default.aspx
Thanks for the info, I will look into this as suggested. I have a
question, though crude, please help me understand this:
Apologies - I have obviously. not explained clearly enough.
I read the Excel object in memory
If you do this server-side, it is only a matter of time before your app
crashes. Office is not designed to be used in this way, which is the reason
that Microsoft don't support it. Please read the links I supplied, paying
particular attention to sections such as:
"Caution. Automation of any Office application from an unattended,
non-interactive user account is risky and unstable. A single error in code
or configuration can result in a dialog box that can cause the client
process to stop responding (hang), that can corrupt data, or that can even
crash the calling process (which could bring down your Web server if the
client is ASP)."
"Warning. Office was not designed, and is not safe, for unattended execution
on a server. Developers who use Office in this manner do so at their own
risk."
I'm really not making this up...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net