Jeff,
Word, like all other Office apps, is designed to interact
with the end user so it's very difficult to get around
the situation you want to avoid. Here's a knowledge base
article you might fight extremely useful....
PSS ID Number: 257757
Article Last Modified on 10/17/2002
This article was previously published under Q257757
SUMMARY
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 Active Server Pages
(ASP), DCOM, or an 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.
NOTE: In this context, the term "server-side" also
applies to code that is running on a Microsoft Windows NT
or Microsoft Windows 2000 workstation, provided that it
is running from a WinStation other than the interactive
station of the user that is logged on. For example, code
that is started by Task Scheduler under the SYSTEM
account runs in the same environment as "server-side" ASP
or DCOM code, and therefore experiences many of the same
issues. For more information on WinStations and COM, see
the "More Information" and "References" sections.