Diego,
You need to qualify "poor performance" before you're able to hold the
application to any metric. But, I can tell you this: I have designed and
implemented a fairly complex application using OWC 9 in the past. Basically,
it entailed server-side generation of spreadsheets containing multiple sheets
(sometimes 15+!) ranging in size from 50K to 250K. I was able to pull about
25 concurrent users from it with an average response time of around 6 seconds
for the reports with multiple testing tools. The hardware is typical fare:
Dell PowerEdge, dual 2.1 procs, 2GB RAM. The clincher: VB6! It's been in
production for around 10 months under a load of 20+ users at peak usage with
no performance problems. This will satisfy most line of busines application
requirements, but if you're trying to do a high-availability Internet site,
good luck.
One caveat is that OWC does not natively support some pretty commonly used
Excel OM members. Notably: WrapText and PageSetup options. However, this is
pretty easy to get around by loading the XMLData property into a DOMDocument
and manipulating the XMLSS schema directly before you stream or save it.
(Bonus: manipulating the PageSetup options don't require printer drivers on
the server if you just deal with the raw XML
Anyhow, I don't think you need to worry too much unless you need to support
more than 30 or 40 concurrent users doing some pretty serious crunching -
like generating 1MB spreadsheets or some other such crazy notion.
Of course, as Alvin says, no need to worry at all on the client-side.
Good luck,
Mudge
Thank for your answer. I checked your web site, and one
questioms comes to my mind.
My application uses a OWC 9.0 as input to a data base.
The inputs are 20 data per person once a month, the worst
scenario 20 users at the same time. I doesn´t seem like a
lot of work right ? But I´m worried because I read in your
web site an other places about some poor performance of
OWC 9.0
Do you think OWC are going to do ok this job?
Regards,
Diego
-----Original Message-----
Three answers for this:
- Ignorance
- Licensing
- Poor documentation
That'll change as soon as my book hits the shelves. Read a sample chapter on
http://tinyurl.com/27cok
--
Regards,
Alvin Bruney
[ASP.NET MVP
http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here...
http://tinyurl.com/27cok
diego said:
Hi:
The question is simple: Which are the flaws or
disadvantages of using OWC ?
I'm receiving an application that uses a Microsoft office
web components spreadsheet (OWC) as input to a data base.
The system look very friendly for user, because it is
Excel, and therefore you can do the usual copy paste
function.
Considering this advantage, I found very strange to don't
see more applications using OWC.
Any comments ?
Thanks,
Diego
.