Xpertdoc takes Word documents and run (merge) them efficiently server side, on premise or from the cloud, for interactive and batch letter generation. CGU, a large insurance group, uses this for generating, auditing, printing and mailing hundreds of letter per day. Here's what they have to say about it: http://www.youtube.com/watch?v=xbqWiFt5dUA&feature=channel&list=UL Symetra Life Insurance integrated it with their customer relationship management (Dynamics CRM), integrating 450 letter templates in 3 weeks.
My organisation is also looking to tackle a problem similar to this and I can share with you some of the things I've found. We're not doing it yet, still in the design stage so take the following with that in mind.
Your situation also depends on the required format at the mailing house - at the moment they must be accepting Word 97 documents, could they also accept XML, DOCX, PDF or something else?
There's a commercial product called Intelledox that lets you use Word 2003 (possibly as early as Word 2000?) as a template designer and then assemble documents from data sources which can be databases, web services etc. Looks like a pretty interesting product, depends on your budget though. This would probably rate highly on your criteria for end user template design.
You could look at the Open XML SDK which allows you to generate DOCX (Word 2007) files programmatically. Your business users would generate a template in Word and supply it to a developer who would then likely create an XSLT. This XSLT is then used at run time to programmatically replace the contents of the base Word document template. This doesn't require Word on the server, just the .NET DLLs that are part of the SDK. Downside to this is it requires a bit of developer processing each time a new template is generated.
I've also considered the reporting approach too - we use SQL Server Reporting Services and that could be used to generate the merged document. It supports Word, Excel, PDF and other export formats. The downside to this is that it also usually requires a developer to design the report. You could deploy the SQL Server Reporting Services Report Builder which is intended for power users to generate their own reports. If you consider this approach make sure it's SQL Server 2008 (Report Builder 2.0), apparently Report Builder v1.0 is pretty poor.
If the mailing house accepts XML you could supply the mailing house with an XSLT file and just send the data, rather than the assembled document. Not sure if the print house you use accepts that, or if you need to keep a copy of the completed document internally for auditing purposes.
Lastly it might be worth a look at the XPS format. Not sure how the templates for this would be design, it might be programming-heavy too.
嗯，对于各种类型的报告，我使用了 Crystal Reports，它允许您轻松地从数据库中检索信息并填写表格。您可以使用 PDF 或 HTML 格式。
Well, for all kinds of reporting I used Crystal Reports, which allows you to easily retrieve information from database and fill in the form. You may use PDF or HTML format for that.
但这并不意味着您不能使用office来创建模板。 Office 文件 (.docx) 是一个 zip/压缩的 xml 文件，可以通过文本操作进行处理。
假设该过程是基于服务器的或不受监控的，我建议 a) 将所有模板升级为 Office 文件 (.docx)。 b) 使用office 2007维护模板 c) 编写或找到一个可以获取 (.docx) 文件、解压缩它们并替换合并字段的程序。注意这个答案取决于模板的复杂性。有许多程序可以处理文本替换等。 d) 运行一个可以将 docx 转换为 pdf 的程序。假设该文档不需要后续修改。找到 docx 到 pdf 是可能的。
你的模板简单吗？或者文档中是否有嵌套数据、条件格式以及其他此类复杂性？
My company has just recently dealt with this issue and we were using even more recent word 2003.
Firstly the use of Office products in a server style environment is not supported by microsoft and my experience will cause you alot of pain. Does the Vb.net application run on a client machine where a user can interact with the program or on a central server (you mentioned dedicated machines)
But this does not mean you cannot use office to create the templates. The office file (.docx) is a zip/compresseed xml file, which can be processed by text manipulation.
assuming the process is server based or not monitored, I would recommend a) upgrade all your templates to office files (.docx). b) use the office 2007 to maintain the templates c) either write or find a program that can take the (.docx) files, unzip them, and replace the merge fields. NOte this answer depends on the complexity of your templates. There are many programs that can deal with text replacement etc. d) run a program that can convert docx to pdf. Assuming the document does not require subsequent modification. finding a docx to pdf is possible.
are your templates simple? or do you have nested data, conditional formatting in the document and other such complexities?
We built something very similar at my company a few months ago. We used a library called DocIO by Syncfusion. The users create normal documents using MS Word (2003 or 2007) with standard Mail-Merge fields in them. These documents are then uploaded and stored in the application's database. We then use the DocIO library to do a mail-merge, passing in a DataTable of values to merge on:
byte[] templateDocument = . . .
DataTable data = . . .
Stream templateDocStream = new MemoryStream(templateDocument);
mailmergeDoc = new DocIO.WordDocument(templateDocStream);
mailmergeDoc.MailMerge.Execute(data);
We can then send the document down to the browser like this
Depending on the complexity of your letters layout, WPF might be a good option.
It's part of the .NET framework so you don't have to rely on any third party library's or apps which may not be updated the future. Which hopefully avoid a repeat of the issues you have with Office 97.
I know you've said price isn't an issue, but it is also free.
发布评论
评论（8）
Xpertdoc 获取 Word 文档并在服务器端、本地或云端高效运行（合并）它们，以进行交互和批处理信代。
CGU 是一家大型保险集团，每天使用它来生成、审核、打印和邮寄数百封信件。以下是他们对此的看法：
http://www.youtube.com/watch?v=xbqWiFt5dUA& ;feature=channel&list=UL
Symetra Life Insurance 将其与客户关系管理 (Dynamics CRM) 集成，在 3 周内集成了 450 个信件模板。
Xpertdoc takes Word documents and run (merge) them efficiently server side, on premise or from the cloud, for interactive and batch letter generation.
CGU, a large insurance group, uses this for generating, auditing, printing and mailing hundreds of letter per day. Here's what they have to say about it:
http://www.youtube.com/watch?v=xbqWiFt5dUA&feature=channel&list=UL
Symetra Life Insurance integrated it with their customer relationship management (Dynamics CRM), integrating 450 letter templates in 3 weeks.
我的组织也在寻求解决与此类似的问题，我可以与您分享我发现的一些事情。我们还没有这样做，仍处于设计阶段，因此请记住以下几点。
您的情况还取决于邮寄公司所需的格式 - 目前他们必须接受 Word 97 文档，他们还可以接受 XML、DOCX、PDF 或其他格式吗？
有一个名为 Intelledox 的商业产品，它可以让您使用 Word 2003（可能早在 Word 2000？）模板设计器，然后从数据源（可以是数据库、Web 服务等）组装文档。看起来是一个非常有趣的产品，但取决于您的预算。这可能会高度符合您的最终用户模板设计标准。
您可以查看 打开XML SDK 允许您以编程方式生成 DOCX (Word 2007) 文件。您的业务用户将在 Word 中生成模板并将其提供给开发人员，然后开发人员可能会创建 XSLT。然后在运行时使用此 XSLT 以编程方式替换基本 Word 文档模板的内容。这不需要服务器上有 Word，只需要 SDK 中的 .NET DLL。这样做的缺点是每次生成新模板时都需要开发人员进行一些处理。
我也考虑了报告方法 - 我们使用 SQL Server Reporting Services，它可用于生成合并的文档。支持Word、Excel、PDF等导出格式。这样做的缺点是它通常还需要开发人员设计报告。您可以部署 SQL Server Reporting Services报告生成器，旨在供高级用户生成自己的报告。如果您考虑这种方法，请确保它是 SQL Server 2008（Report Builder 2.0），显然 Report Builder v1.0 相当差。
如果邮寄公司接受 XML，您可以向邮寄公司提供 XSLT 文件并仅发送数据，而不是组合文档。不确定您使用的印刷厂是否接受这一点，或者您是否需要在内部保留已完成文档的副本以供审核之用。
最后，XPS 格式可能值得一看。不确定这个模板是如何设计的，它也可能需要大量编程。
无论如何，希望这对您的思考有所帮助！
My organisation is also looking to tackle a problem similar to this and I can share with you some of the things I've found. We're not doing it yet, still in the design stage so take the following with that in mind.
Your situation also depends on the required format at the mailing house - at the moment they must be accepting Word 97 documents, could they also accept XML, DOCX, PDF or something else?
There's a commercial product called Intelledox that lets you use Word 2003 (possibly as early as Word 2000?) as a template designer and then assemble documents from data sources which can be databases, web services etc. Looks like a pretty interesting product, depends on your budget though. This would probably rate highly on your criteria for end user template design.
You could look at the Open XML SDK which allows you to generate DOCX (Word 2007) files programmatically. Your business users would generate a template in Word and supply it to a developer who would then likely create an XSLT. This XSLT is then used at run time to programmatically replace the contents of the base Word document template. This doesn't require Word on the server, just the .NET DLLs that are part of the SDK. Downside to this is it requires a bit of developer processing each time a new template is generated.
I've also considered the reporting approach too - we use SQL Server Reporting Services and that could be used to generate the merged document. It supports Word, Excel, PDF and other export formats. The downside to this is that it also usually requires a developer to design the report. You could deploy the SQL Server Reporting Services Report Builder which is intended for power users to generate their own reports. If you consider this approach make sure it's SQL Server 2008 (Report Builder 2.0), apparently Report Builder v1.0 is pretty poor.
If the mailing house accepts XML you could supply the mailing house with an XSLT file and just send the data, rather than the assembled document. Not sure if the print house you use accepts that, or if you need to keep a copy of the completed document internally for auditing purposes.
Lastly it might be worth a look at the XPS format. Not sure how the templates for this would be design, it might be programming-heavy too.
Hope this helps with your thinking anyway!
Office 2007 SDK 不是可以立即处理这种情况吗？
或者，您可以考虑绕过 Office 并直接使用 wpf，使用商业富文本编辑器。
Doesn't the office 2007 SDK deal with this sort of situation out of the box?
Alternatively you could look at sidestepping office and using wpf directly, with a commercial Rich text editor.
嗯，对于各种类型的报告，我使用了 Crystal Reports，它允许您轻松地从数据库中检索信息并填写表格。您可以使用 PDF 或 HTML 格式。
Well, for all kinds of reporting I used Crystal Reports, which allows you to easily retrieve information from database and fill in the form. You may use PDF or HTML format for that.
我的公司最近才处理这个问题，我们使用的是更新的word 2003。
首先，微软不支持在服务器风格环境中使用Office产品，我的经验会给你带来很多痛苦。 Vb.net应用程序是否运行在用户可以与程序交互的客户端计算机上或中央服务器（您提到的专用计算机）上，
但这并不意味着您不能使用office来创建模板。 Office 文件 (.docx) 是一个 zip/压缩的 xml 文件，可以通过文本操作进行处理。
假设该过程是基于服务器的或不受监控的，我建议
a) 将所有模板升级为 Office 文件 (.docx)。
b) 使用office 2007维护模板
c) 编写或找到一个可以获取 (.docx) 文件、解压缩它们并替换合并字段的程序。注意这个答案取决于模板的复杂性。有许多程序可以处理文本替换等。
d) 运行一个可以将 docx 转换为 pdf 的程序。假设该文档不需要后续修改。找到 docx 到 pdf 是可能的。
你的模板简单吗？或者文档中是否有嵌套数据、条件格式以及其他此类复杂性？
My company has just recently dealt with this issue and we were using even more recent word 2003.
Firstly the use of Office products in a server style environment is not supported by microsoft and my experience will cause you alot of pain. Does the Vb.net application run on a client machine where a user can interact with the program or on a central server (you mentioned dedicated machines)
But this does not mean you cannot use office to create the templates. The office file (.docx) is a zip/compresseed xml file, which can be processed by text manipulation.
assuming the process is server based or not monitored, I would recommend
a) upgrade all your templates to office files (.docx).
b) use the office 2007 to maintain the templates
c) either write or find a program that can take the (.docx) files, unzip them, and replace the merge fields. NOte this answer depends on the complexity of your templates. There are many programs that can deal with text replacement etc.
d) run a program that can convert docx to pdf. Assuming the document does not require subsequent modification. finding a docx to pdf is possible.
are your templates simple? or do you have nested data, conditional formatting in the document and other such complexities?
几个月前，我们在我的公司构建了非常相似的东西。我们使用了一个名为 Syncfusion 的 DocIO 的库。用户使用 MS Word（2003 或 2007）创建普通文档，其中包含标准邮件合并字段。然后，这些文档被上传并存储在应用程序的数据库中。然后，我们使用 DocIO 库进行邮件合并，传入要合并的值的 DataTable：
然后我们可以像这样将文档发送到浏览器
We built something very similar at my company a few months ago. We used a library called DocIO by Syncfusion. The users create normal documents using MS Word (2003 or 2007) with standard Mail-Merge fields in them. These documents are then uploaded and stored in the application's database. We then use the DocIO library to do a mail-merge, passing in a DataTable of values to merge on:
We can then send the document down to the browser like this
根据字母布局的复杂性，WPF 可能是一个不错的选择。
它是 .NET 框架的一部分，因此您不必依赖任何将来可能不会更新的第三方库或应用程序。希望这可以避免重复使用 Office 97 时遇到的问题。
我知道您说过价格不是问题，但它也是免费的。
Depending on the complexity of your letters layout, WPF might be a good option.
It's part of the .NET framework so you don't have to rely on any third party library's or apps which may not be updated the future. Which hopefully avoid a repeat of the issues you have with Office 97.
I know you've said price isn't an issue, but it is also free.
微软报告查看器。
Microsoft ReportViewer.