Report Generation Toolkit (Word) : How to use correctly bookmark and cross-reference without "Error! Reference source not found"

[nki]

Hi,

I try to generate a report using a template. In my template I use some cross-reference to refer to one bookmark. For exemple in the first page I created a bookmark for my name and in the header I created a cross-reference refer to my name. The problems is when I run my VI the bookmark actualise perfectly but the cross-reference refer to the bookmark can't actualise with the same value and generates an error : "Error! Reference source not found".
Can somebody help me please!

Nki

[User002]

Just to clarify:

When you write to a bookmarked location in word that has a cross-reference, the reference shows that the source is not found?  Does this happen every time, or just with this template?  Have you tried it in another project?

Also, what versions of LabVIEW are you using?  And Microsoft Office?

[nki]

Hi,

When i create the word template, the bookmaks and the cross-reference referred to the bookmark update correctely. The problem is when I try to change the bookmark using "report generation from template vi" the bookmark change but not the cross-reference and the error generated is "Error! Reference source not found". 

I make coople reasherch and i think they have no solution for this because : "if the text in a heading referred to in a cross-reference is revised, the cross-reference to the heading may no longer work" (http://office.microsoft.com/en-us/word-help/troubleshoot-cross-references-HP005189368.aspx).

To "resolved" this problem I create an other bookmark in the template who have the same value white the principle bookmark.   

I use Labview 2011 and Micosoft office 2010.

[User002 · Accepted solution]

Unfortunately, since it is an error within Word, there's not much we can do about it.  But you found a great workaround - good troubleshooting.

[Neercs]

Hi everybody,

I have exactly the same issue with cross-reference in a Word template.

Does this issue has been solved now in 2015 ?

Cheers

[Agamemone]

Unfortunately this issue is still inherent of Microsoft. The Report Generation Toolkit has not changed.