http://blogs.msdn.com/joshpoley/archive/2008/04/14/automating-doc-to-pdf-conversion.aspxThe COM object model exposed by Microsoft Word gives us the power to save any document which Word can recognize into a PDF file (as long as you've downloaded and installed the XPS and PDF exporter first). And it turns out that programmatically convertingen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/joshpoley/archive/2008/04/14/automating-doc-to-pdf-conversion.aspx#8393992Mon, 14 Apr 2008 21:48:50 GMT91d46819-8472-40ad-a661-2c78acb4018c:8393992Christopher_G_Lewis<P>So given this KB article: <A href="http://support.microsoft.com/default.aspx?scid=kb;EN-US;257757" target=_new rel=nofollow>http://support.microsoft.com/default.aspx?scid=kb;EN-US;257757</A> </P> <P>What would you recommend on doing this on a server through ASP or ASP.NET.</P> <DIV style="BORDER-RIGHT:black 1px solid;PADDING-RIGHT:5px;BORDER-TOP:black 1px solid;PADDING-LEFT:5px;PADDING-BOTTOM:5px;MARGIN-LEFT:5px;BORDER-LEFT:black 1px solid;PADDING-TOP:5px;BORDER-BOTTOM:black 1px solid;BACKGROUND-COLOR:#444444;">The answer will ultimately depend on what exactly you are trying to accomplish (what is the scale, etc). But if I was trying to do this as an internal tool with Office (i.e. not wanting to spend the money on a commercial application to do this for me) then I would probably setup a separate server to do the conversions offline. Have a front-end web server submit "jobs" to the backend processing server who will do the conversion then send email when done. By running on a separate box, you can run office within a user context and can deal with any cleanup issues without destroying the user facing application. - josh</DIV>