MS office report

Question

Hi, I am trying to generate a report using the MS office express vi and after follow the instructions in the manuals and check the examples I cant fill a table predefined in my own template!! and I get an error
Error -41110 occurred at NI_ReportGenerationToolkit.lvlib:ex_RGT_Append Anything To Report.vi -> NI_ReportGenerationToolkit.lvlib:subMS Office Report Block.vi -> test_report.vi:MS Office Report.vi-> test_report.vi
while processing the module_ID input.
I am using labview 2011. attached is a vi  that I wrote to study only the report generation.
I appreciate any suggestion.
Attachments:
test report.vi ‏22 KB
SOP_103_template.dot ‏32 KB
base_info_Report.vi ‏17 KB

Answer 1

Well, you have certainly picked a fairly challenging task for LabVIEW to undertake!  I've thought about how I would do this (or even if I would do this), and have some observations.
A Word Template does not necessarily make life easier if you are "driving" Word from LabVIEW.  It is designed for human interaction, with the (human) ability to tab around and ensure that the cursor is in the correct field for inserting an element.
In particular, your Parts List does not "tab nicely".  In particular, it will expect exactly 1 entry in the UNL Batch No., and precisely 4 Parts entries (as you tab around, notice you enter the Batch No. field four times).
If I were doing this, I would generate the entire Report "on the fly", that is, I'd start with a blank Report, generate the heading ("Manufacturing of modules ..."), generate a Report Header Table (Date, Start, Finish, Operator, etc.), generate a Parts List table, and generate a Comments section.
I would certainly "encapsulate" the messy code for each of these steps in its own sub-VI.  Thus my Report would look something like this:
Each of the sub-VIs generate part of the Report.  Header generates the static text at the top.  Report Info generates the Date, Time, Operator, etc. part of the report, Parts List generates the Parts List table, and Comments generates the Comments at the end.
The Report "data" is encapsulated in four variables:
Report Info is a cluster with entries Date, Start Time, Finish Time, Operator, etc.
Parts List is an array of clusters (UNL Batch, BBM ID, and HDI S/N).
Comments is a cluster with entries Orientation, Glueing, etc.
Report Path is the path and name of the output Word document.
Report Info can be formatted as a table of two columns.  Each entry has a fixed string (for example, "Date:") and a variable (the value in Report Info.Date, the cluster element).  You can format the table with top and bottom borders if you want that look.
Parts List is fairly complicated.  It has some "pure text" (the string "List id of parts ...") and a Table.  The Table is fairly straight-forward, with a fixed Header and a style for borders and lines.  To get the UNL Batch formatting as a single cell, you can try to merge cells (based on where the UNL Batch values remain constant).
Comments can just be treated as ordinary text, with "header strings" (such as "Orientation:") written before the value in the corresponding Comment cluster element (e.g. Orientation) is written.
I can say, with some confidence, that the Snippet above will, in fact, produce a Report that follows your Template, once you handle the "details" of coding those four sub-VIs.  Take a look at the Word-specific sub-Palette in the Report Generation Palette, and in the Word Tables sub-sub-Palette.  
Bob Schor