Microsoft Office Tutorials and References
In Depth Information
The Excel Workbook (*.xlsx) file format is the default when you save a new file in Excel 2007. It is a
ZIPcompressed file composed of several XML parts and uses the Office Open XML standard, which makes it
easy to read and update programmatically.
The Excel Binary Workbook (*.xlsb) file format is similar to the Excel Workbook file format. It is also a
ZIP-compressed file, but instead of XML parts, it has binary parts. The binary format is more efficient
to load and save, so you should use it in scenarios in which the performance impact is important.
Excel 2007 has the following additional macro-enabled file formats, which might contain code:
Excel Macro-Enabled Workbook (*.xlsm)
Excel Macro-Enabled Template (*.xltm)
Excel Add-In (*.xlam)
These formats are not supported by Excel Services. If you have a macro-enabled workbook that you want
to port to the server, save it as an Excel Workbook or Excel Binary Workbook and remove the code from
The Excel 2007 Template (*.xltx) file format is not supported on the server. If you use the template
to create a new workbook, save it in one of the two supported file formats when publishing to the
None of the other older file formats are supported. These include the Excel 97-2003 Workbook (*.xls)
file format, which was the default until Excel 2003, and the Web Page file formats (*.mht; *.mhtml; *.htm;
*.html). When you are porting existing files that were authored with a previous version of Excel, save
them with one of the new Excel 2007 supported file formats when publishing to Excel Services.
If you try to open a file with one of the unsupported file formats, you will get the error message shown
in Figure 4-1.
You must use a supported file format to successfully open files in Excel Services. There are a number of
Excel features that are not supported on the server, and they are detailed in this section. If a workbook
has any of these features, the server will fail to open it.
The advantage of this behavior is that if a workbook successfully opens on the server, you know it will
have fidelity with Excel. The disadvantage is that you cannot have a workbook with an unsupported
feature and just have the server ignore it. For example, you might have VBA macros that are useful
during the authoring of the workbook on the client and are not needed on the server. However, you will not
be able to save the workbook to the server, because VBA macros are not supported. The workaround is
to have two copies of the workbook, one with the macros that will be used on the client, and one
without that will be published to the server.