XLimits - Limitationen der Office Web Components

Limitationen der Office Web Components

Limitationen der Office Spreadsheet Component

Berechnungsunterschiede zwischen Office Spreadsheet und Excel

Online-Hilfen mit weiteren Informationen

Limitationen der Office Web Components

The Microsoft Office 2000 Web Components provide Web developers with spreadsheet, charting, and pivot table capabilities to make Web pages more dynamic. The components were developed as client-side ActiveX controls that can be used inside of Microsoft Internet Explorer.

The functionality of the components, however, has led many developers to use them in server-side solutions, such as in Active Server Pages (ASP) or COM+ to build and export charts. While the components can be used in this way, limitations can hinder the stability and performance of server code, and may make the components problematic in a large-scale server-side solution.

Microsoft does not recommend that you use the Office 2000 Web Components in a server-side solution. Several known limitations prevent the components from functioning properly in a highly reentrant, multi-threaded, non-interactive environment. Among the problems that you may experience are the following:

Slow execution or poor performance: The Office 2000 Web Components were designed for the multiple single-threaded apartment (STA) environment of Internet Explorer, and not the multi-threaded apartment (MTA) environment of most server-side applications. The protection for thread concurrency for the Office 2000 Web Components was not designed for the high volume, multi-threaded calls that are typical of a Web service, and can therefore impact performance. For example, the Office 2000 Web Components protect a number of shared memory blocks with the same critical section, so that threads that do not modify a memory section may still be blocked if another thread modifies the memory section. Moreover, many of the functions for processing were imported from other Office sources that were designed in a single-threaded model, and these sections of code cannot run concurrently.
Out-of-memory errors: The Office 2000 Web Components uses a static build of the Microsoft Office 9.0 office library to handle memory management. The memory allocation functions of the Microsoft Office 9.0 office library are designed for the client side, and do not expect the loads and concurrent requests that are typical in a server-side solution. This may limit the amount of memory that the components have available to them, regardless of the amount of memory that is free on the computer.
Automation errors at random times: The Office 2000 Web Components use a few state variables that are not fully protected, and if the variables change while a function is running, they can cause the function to fail unexpectedly. Functions that require asynchronous processing (such as requesting data from a data source, or calculating cell values in a spreadsheet) are more likely to generate such errors if multiple threads are automating concurrently.
Thread deadlocks: In some situations, the Office 2000 Web Components may encounter race conditions that lead to indefinite wait states or global exceptions, which can orphan a thread and cause a loss of resources. These situations typically occur when the components are "stressed"; for example, this may occur when a high number of clients make concurrent requests to the server, and each request creates, automates, or destroys its own component instance. Pooling instances can minimize the risk of deadlock.

The problems with the Office 2000 Web Components that are listed above are design limitations that are consistent with their intended use as client-side ActiveX controls. No workaround or fix is available for these Office 2000 Web Components limitations.

Many of these issues have been resolved with the Microsoft Office XP Web Components. If you currently use, or plan to use, the Office 2000 Web Components in your Web solution as server-side components, you should consider upgrading to the Office XP Web Components.

INFO: Limitations of Office 2000 Web Components When Used Server-Side
http://support.microsoft.com/?kbid=317316

Limitationen der Office Spreadsheet Component

In Microsoft Excel, a single formula can contain up to seven levels of nested functions. However, the Office Spreadsheet Component does not have this limit. Actually, no limit exists for nesting functions other than the limit of 1,024 characters in a single formula. However, if you plan to export the Office Spreadsheet to Microsoft Excel, you should limit nesting functions to seven levels because you cannot exceed the limit in Excel. When you export an Office Spreadsheet to Excel, the cell that contains a formula exceeding this limit will only contain the value of that formula.

Weitere Informationen

Limitationen-Fachartikel: Maximale Verschachtelungstiefe in Funktionen (Artikel xllimit8)

The SOSCQ Page: Fragen und Antworten: Gibt es bekannte Probleme beim Speichern einer Spreadsheet Web Component-Tabelle als Excel-Arbeitsblatt?

Features and Limitations of XML Spreadsheet Format in Excel 2002
http://office.microsoft.com/assistance/2002/articles/xlFeaturesLimitationXmlSpread.aspx

Excel Feature	Result when saved as XML Spreadsheet
1904 date system	Retained
Asterisks that mark totals for OLAP data	Retained
Auditing tracer arrows	Not retained
Background refresh, retrieving data for each item in a page field individually	Retained
Calculated fields	Retained
Calculated items	Retained
Cell comments	Retained
Changes to Excel source data	Retained
Character and cell formatting	Retained
Chart and other graphic objects	Not retained
Chart sheets, Macro sheets, Dialog sheets	Not retained
Conditional formatting	Retained
Custom calculations	Retained
Custom sort order	Retained
Custom views	Not retained
Customized error values and empty cell values	Retained
Data consolidation	References are not retained.
Data validation restrictions and messages	Retained
Distributed alignment	Retained
Drawing object layers	Not retained
External data ranges	Retained
Grouped items in fields	Retained
Indented formats	Retained
Indented text	Retained
Labels in formulas	Retained
Multiple fonts in a single cell	Retained
Number formats	Retained
Offline cube file	Retained
Outlining	Not retained
Page fields in rows or columns	Retained
Password settings	Data in password-protected worksheets and workbooks cannot be saved. To publish data that's protected, do not use a password. You can, however, save a database password with a worksheet query; users will be required to enter the password when the XML Spreadsheet is opened.
Pattern fills	Retained
PivotTable Reports	Retained
Precision as displayed	Retained
Printing and page setup features	Retained
R1C1 reference style	Retained
References to data on other worksheets	Retained
Rotated or vertical text	Retained
Scenarios	Not retained
Shared workbook information	Not retained
Subtotals	Numbers and calculations are retained. Group and outline features are not retained.
Subtotals displayed at the top of item groups	Retained
Thai alignment	Retained
Transition settings for Lotus compatibility	Retained
User-defined function categories	Not retained
Visual Basic for Applications projects	Not retained
Web queries	Retained

Berechnungsunterschiede zwischen Office Spreadsheet und Excel

Text folgt in Kürze...

XL2000: Calculation Differences Between the Office Spreadsheet and Excel
http://support.microsoft.com/?kbid=216578

Online-Hilfen mit weiteren Informationen

Component Name	Web Components 9.0	XP Web Components	Description
Chart	MSOWCDCH.chm	OWCDCH10.chm	Chart component design-time reference
PivotTable	MSOWCDPL.chm	OWCDPL10.chm	PivotTable component design-time reference
Spreadsheet	MSOWCDSS.chm	OWCDSS10.chm	Spreadsheet component design-time reference
Spreadsheet	MSOWCFUN.chm	OWCFUN10.chm	Spreadsheet component built-in function reference
DataSource, Chart, PivotTable and Spreadsheet	MSOWCVBA.chm	OWCVBA10.chm	Programming reference for all components

HOW TO: Find Office Web Components (OWC) Programming Documentation and Samples
http://support.microsoft.com/?kbid=319793

Haben Sie Fragen, Anregungen oder einen Fehler entdeckt?
Kontakt zum Autor

Kostenlose Zähler