Developers can use Automation to Microsoft Office to build custom solutions that utilize the capabilities and features that are built into the Office product. While such programmatic development can be implemented on a client system with relative ease, there are a number of complications that can occur if Automation is to take place from server-side code such as Microsoft Active Server Pages (ASP), DCOM, or a Windows NT Service.
This article discusses the complications that developers may face, offers alternatives to Automation that can speed performance, and suggests ways to configure Office if server-side Automation is unavoidable. Developers should be aware, however, that the suggestions provided below are for informational purposes only. Microsoft does not recommend or support server-side Automation of Office.