T
Thomas Bushman
I have a web application that is doing a Word mail merge. During the design,
our IT folks decided they definitely did not want Word being installed on the
web server, nor did they want the Interop API's being installed on each local
machine since they would need to be reinstalled for EVERY update to Office.
What I did then was have an application which has a server side script block
that creates a dynamic CLIENT side block that sets variables based upon the
values in the database. There is then a following client side block that
opens up the word object, loads the template file, does the mail merge, saves
the document to the local machine, then redirects to browsing that completed
form. A template is below:
<%@ Language=VBScript %>
<html>
<head>
</head>
<body>
<%
Response.Write(vbCRLF & "<script language=vbscript>" & vbCRLF & "<!--" &
vbCRLF)
' Make our db connection
' Get our data and write out each variable setting
our IT folks decided they definitely did not want Word being installed on the
web server, nor did they want the Interop API's being installed on each local
machine since they would need to be reinstalled for EVERY update to Office.
What I did then was have an application which has a server side script block
that creates a dynamic CLIENT side block that sets variables based upon the
values in the database. There is then a following client side block that
opens up the word object, loads the template file, does the mail merge, saves
the document to the local machine, then redirects to browsing that completed
form. A template is below:
<%@ Language=VBScript %>
<html>
<head>
</head>
<body>
<%
Response.Write(vbCRLF & "<script language=vbscript>" & vbCRLF & "<!--" &
vbCRLF)
' Make our db connection
' Get our data and write out each variable setting