| Q: |
What
is OfficeWriter? |
| A: |
OfficeWriter
is a web-based solution that enables the creation of native Excel
and Word documents populated from any data source. Designed for server
usage, it is high performance and scalable. It replaces the use of
Microsoft Office on the server. |
| Q: |
Why
should I consider OfficeWriter? |
| A: |
Here
are some key benefits offered by OfficeWriter:
- Flexible, customized reporting offering design-time and runtime
control
- Support for ad-hoc report creation & delivery or batch processing
- Enables all features of Office 97-2007
- Integration with Reporting Services, SharePoint, CRM, and other
BI Tools
- “HotCell” functionality provides updating of data using
Excel or Word as a form
- OfficeWriter can be used to extract content from Excel and Word
files |
| Q: |
What
are OfficeWriter’s server requirements? |
| A: |
There
are four primary server requirements to run OfficeWriter in a server-based
application:
- Windows 2000, XP or 2003 Server
- IIS 5.0 or higher
- Microsoft .NET Framework Redistributable
- J# Redistributable Package |
| Q: |
Will
I also need to license Microsoft Office? |
| A: |
OfficeWriter
replaces the need for Microsoft Office on the server. It creates Excel
workbooks and Word documents that can include any features of Excel
and Word 97 – 2007 without involving Office in the process.
However, recipients must have Office installed locally to open and
manipulate OfficeWriter generated files. |
| back
to top |
| Q: |
What
software is required on the client to view OfficeWriter exports? |
| A: |
To
open a document generated by OfficeWriter for Word, you can use:
- Microsoft Word 97 – 2007
- Microsoft’s free Word Viewer
- Any application that supports the Word Format, such as StarOffice
or OpenOffice for Unix
To open a workbook generated by OfficeWriter for Excel, you can use:
- Microsoft Excel 97 – 2007
- Microsoft’s free ExcelViewer
- Any application that supports the Word Format, such as StarOffice
or OpenOffice for Unix |
| Q: |
Is
OfficeWriter designed for use in .NET applications? |
| A: |
OfficeWriter
is the perfect solution for developing .NET applications. It provides
a set of pure .NET classes for the creation of Excel and Word in the
form of assemblies that can be easily referenced in a .NET project. |
| Q: |
Is
OfficeWriter for Excel available for use in ASP? |
| A: |
The
OfficeWriter suite includes legacy COM versions of the “ExcelTemplate”
and “ExcelApplication” APIs in the form of a DLL that
can be referenced from an ASP script and which will allow for all
features of Excel file creation or content extraction. |
| Q: |
Is
OfficeWriter for Word available for use in ASP? |
| A: |
OfficeWriter
for Word was designed from inception in the form of a pure .NET assembly.
A COM callable wrapper is provided to enable access to the “WordTemplate”
API only. The more robust “WordApplication” API is not
available in ASP. The server must have the .NET framework and J# runtime
installed in order to enable use even in ASP. |
| Q: |
What
is the procedure for installing OfficeWriter on a server? |
| A: |
A
full installation of OfficeWriter can be accomplished by running the
automated installer (“OfficeWriter-Installer-X.X.X-WIN32.exe”)
on the server. There is only one installer for all versions of OfficeWriter
(SE or EE, evaluation or permanent). The license key, typically provided
with the download instructions, or sent in a follow-up email from
our sales department, unlocks the features of a specific edition. |
| Q: |
How
do I update a license key? |
| A: |
Once
OfficeWriter is installed locate the “LicenseManager.exe”
in the “OfficeWriter” install’s top-level folder
(typically located at “…\Program Files\SoftArtisans\OfficeWriter”).
Open the utility and copy/paste the key in the “New Key”
textbox and click the “Add/Upgrade” button. You must stop
and restart IIS or reboot the server for the update to take effect. |
| Q: |
Is
their a minimal installation of OfficeWriter? |
| A: |
If
you are using OfficeWriter as part of a .NET solution, you can copy
the project to the server with the OfficeWriter assembly(s) included.
But, you also need to inject the provided license key in the target
server’s registry. This can be done by deploying the “LicenseManager.exe”
or securing a customized .reg file from SoftArtisans. |
| Q: |
What
are the key differences between the Standard and Enterprise Editions
of OfficeWriter? |
| A: |
The
Standard Edition provides access to the “ExcelTemplate”
and “WordTemplate” design-time approaches to Excel and
Word generation, as well as the majority of the SQL Server Reporting
Services (SSRS) Integration functionality. The Enterprise Edition
adds the ad-hoc runtime approach enabled by accessing the “ExcelApplication’
and “WordApplication” programmatic APIs as well as the
balance of SSRS integration features. |
| Q: |
What
are the benefits of employing the “Template Approach”
enabled in OfficeWriterSE? |
| A: |
Excel
and Word are used to design the report in the form of a template that
contains data markers (Excel) or Merge Fields (Word). OfficeWriter
loads the template, merges data, and preserves all features into the
exported file. This approach is well-suited for “canned reports”
and basic reporting needs. It offers:
- Rapid application deployment
- Minimal developer interaction
- High performance throughput with large files |
| Q: |
What
are the benefits of the “Application Approach” enabled
in OfficeWriterEE? |
| A: |
Excel
and Word files can be scripted or opened and customized at runtime
using the “ExcelApplication” and “WordApplication”
programmatic APIs. This provides flexible ad-hoc reporting capabilities.
It offers:
- Base template runtime customizations: pass from template to application
(or vise versa)
- Granular control of formatting and layout
- Ability to open and extract content from workbooks and documents
- Full “HotCell” approach to enable Excel and Word as
form for data updates |
| Q: |
What
edition of OfficeWriter do I need for SQL Server Reporting Services
Integration? |
| A: |
OfficeWriterSE
provides the ability to add full-featured Excel and Word exports to
SQL Server Reporting Services published reports. The OfficeWriterEE
version adds the ability to display report parameters, reporting services
globals and formulas. Plus EE enables the customization of rendered
reports from a .NET intermediary script using the “ExcelApplication”
and “WordApplication” APIs. |
| Q: |
Does
OfficeWriter provide the ability to render Excel or Word exports to
PDF format? |
| A: |
At
the present time OfficeWriter provides only exports in the form of
.doc or .xls output. We are currently investigating support for exporting
to PDF as a future product enhancement. |
| Q: |
Can
I set server-side printing options from an OfficeWriter application? |
| A: |
No,
you will not be able to send OfficeWriter generated documents or workbooks
directly to a printer. OfficeWriter does not provide server-side calculation
of formulas and charts in Excel or pagination in a document. These
must be accomplished by opening them with MS Office prior to printing. |
| Q: |
What ADO.NET data sources can be used with
OfficeWriter? |
| A: |
There are
four primary server requirements to run OfficeWriter in a server-based
application:
- Windows 2000, XP or 2003 Server
- IIS 5.0 or higher
- Microsoft .NET Framework Redistributable
- J# Redistributable Package |
